I've recently tried to upgrade my venue 3840 to 4.4.4 after unlocking the bl and rooting on 4.4.2 but it seems to be a giant pain in the ***. I've downloaded the system image tried flashing it via fastboot with the line fastboot flash system system.img but of course it complains about max image size and once I do get it going, it gives me command errors. Yes, I've tried redownloading and all, no change. I've even tried creating a rom with the inside of the system image and I believe the problem is my updater binary/script. I was just wondering if I could get any help. The tablet isn't booting because again of course things don't always go as planned. I know I can unbrick or 'go back to stock' with dells way however I really don't feel like redoing my data.
I got the 4.4.4 files from here https://www.androidfilehost.com/?fid=95784891001604343 <- this one includes the system extracted
This one includes the system image and boot img https://www.androidfilehost.com/?fid=95784891001602440
If anyone is able to possibly turn this into a rom or even direct me in the right direction, that'd be greatly appreciated! If not, completely understandable. Thank you for your time!
Or if someone could possibly make a stock wiped back up of 4.4.4 , that'd be great as well!
update: got the tablet to boot with a stock 4.4.2 zip from dell however still looking to be able to update to 4.4.4 if possible, thanks!
And apparently I was able to take out the system and boot in the dell source http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/A195/OTA/ and replace it with the 4.4.4 system / boot. I have a bootable 4.4.4 rom. If it's needed for any purposes let me know. Sorry for the basically pointless thread lmao. You'd be amazed at how long it took me to solve this. :silly:
Can you please upload the ROM you created? Was it an AOSP build?
Thanks!
Hi,
Sorry to reply to an old thread. Could you provide some details on what you've done exactly?
I have the same tablet lying around collecting dust since Dell's stock OS is absolute garbage. I am trying to build an AOSP ROM for it just for the sake of experimenting. Could you please help me out?
Thanks for your time.
Related
For reference: We have two Motorola Moto E (XT1021) devices in our family. Both have been unlocked, rooted, and have TWRP installed. They are running Android 4.4.3.
We would like to upgrade to later versions of Android. However, I am getting conflicting answers on a few issues:
(1) If we just return to the stock bootloader and allow the Motorola update process to continue, will it brick our devices? (Some say yes, some say no... any solid answers?)
(2) In order to upgrade to Lollipop, most of the walkthroughs I have seen say to restore to stock firmware. Is this actually necessary?
(3) If it IS necessary to restore to stock firmware, does anyone have a working link to a current XT1021 stock ROM? Unfortunately, I seem to have lost my copy, and every single link that I have found so far is to http://sbf.droid-developers.org/phone.php?device=34 , which is a dead link.
Thanks in advance for your assistance!
1. Most likely. There have been many users reporting hard bricked devices when the did what you are telling. So you shouldn't risk it.
2. No, it is not necessary if you haven't changed the system a bit, and in such a case just unrooting would suffice. But as you were rooted and all, you may have altered it a little. So it is recommended to flash stock as it removes all chances of errors.
3. Working link:http://forum.xda-developers.com/showthread.php?p=54872420
Hope I helped!!!
Harsh862 said:
Hope I helped!!!
Click to expand...
Click to collapse
Thanks for the answers. I'll definitely have to go back to stock then if we want to upgrade. I hate losing all my settings and high scores, but if that's what has to be done, that's what we have to do.
However, the link for the firmware is for Brasil. So it won't work for me. I'm in the United States, and need the US retail global version for the XT1021. Maybe someone else has this? Thanks in advance!
Also, not sure if it makes a difference or not, but we are still on 4.4.3.
LeiraHoward said:
For reference: We have two Motorola Moto E (XT1021) devices in our family. Both have been unlocked, rooted, and have TWRP installed. They are running Android 4.4.3.
We would like to upgrade to later versions of Android. However, I am getting conflicting answers on a few issues:
(1) If we just return to the stock bootloader and allow the Motorola update process to continue, will it brick our devices? (Some say yes, some say no... any solid answers?)
(2) In order to upgrade to Lollipop, most of the walkthroughs I have seen say to restore to stock firmware. Is this actually necessary?
(3) If it IS necessary to restore to stock firmware, does anyone have a working link to a current XT1021 stock ROM? Unfortunately, I seem to have lost my copy, and every single link that I have found so far is to http://sbf.droid-developers.org/phone.php?device=34 , which is a dead link.
Thanks in advance for your assistance!
Click to expand...
Click to collapse
Que 1&2 are basically the same.
Here is a detailed explanation for both.
To update your OS via official OTA, you need unmodified system. The OTA doesn't simply copy files to the system, it patches those files so if a single file is modified the update won't be able to patch it and your phone will soft brick.
Now, to avoid that, it is recommended to flash stock ROM before updating. Its safe but its a lot cause you just need unmodified system. OTA doesn't care about anything else.(stock recovery is needed too.)
So you can just flash the system partitions and stock recovery. This will not remove your data & those high scores.
To flash just extract your rom and execute these commands ONLY.
Code:
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
You will have your stock recovery and unmodified system ready for update.
neo.ank said:
it is recommended to flash stock ROM before updating. Its safe but its a lot cause you just need unmodified system. OTA doesn't care about anything else.(stock recovery is needed too.).
Click to expand...
Click to collapse
Thanks. I guess I'm stuck because I do not have stock recovery files (I could have sworn I had them backed up but I can't find them anywhere) and I am unable to find them online at the moment (all credible links seem to point back to the dead droid-developers link).
If anyone has a copy of the stock files, I'd love to get them.
LeiraHoward said:
Thanks. I guess I'm stuck because I do not have stock recovery files (I could have sworn I had them backed up but I can't find them anywhere) and I am unable to find them online at the moment (all credible links seem to point back to the dead droid-developers link).
If anyone has a copy of the stock files, I'd love to get them.
Click to expand...
Click to collapse
Stock recovery files are available on xda. Why are going to stock for lollipop upgrade. Use a lollipop flashable file which is given on this page. Don't screw up your device. Link-http://forum.xda-developers.com/moto-e/development/rom-motorola-stock-rom-t2935429
I've done some research and it looks as though the file I need is Blur_Version.21.12.34.condor_retuglb.retuglb.en.US which should be Android 4.4.3 for the XT1021 for the GSM phone in the US. But I am unable to find this rom anywhere. The only file I've been able to get is the 4.4.4 and I don't think that flashing just parts of that one to my device is a good idea. I'd still kinda like to keep my original settings... does anyone have the Blur_Version.21.12.34.condor_retuglb.retuglb.en.US file or a link to it? I have done SO many searches on this site but keep running into dead links. (Whatever happened to droid-developers anyway? ALL the links go to them and nothing works....)
Thanks!
Just a quick question about "bump"ed TWRP images and why they might/might not work. I got my G3 a few days ago (came with Lollipop 5.0 stock) and finally got around to rooting it today. Naturally, I wanted to install TWRP after that so I could fire up some custom ROMs later on. I followed the guide in the official Bump! thread and ended up with recovery that wouldn't boot due to a "secure boot error". I then tried flashing the same, bumped, 2.8.7.0 image with Flashify, with the same result. Then I moved on to AutoRec, and for some reason that did the trick - after letting it flash TWRP, I could boot into recovery with no problems. I then flashed the (newer) bumped image I got from the Bump! thread that hadn't worked before and to my bewilderment, it worked as well. Can someone explain to me in broad strokes what exactly made the difference? And, if there is an additional step involved beyond just flashing a bumped TWRP, why is that not mentioned anywhere in the Bump! thread?
Also, from what I understand, "bump"ing an image just means signing it with LG's key that was extracted by the Bump! and open bump! developers. If that is the case, why are there still un-bumped recovery images floating around? What use are those to anyone, if aboot will refuse to boot them?
Cheers,
George
P.S. If there is a thread/post already out there somewhere (I'm pretty sure there is, but I couldn't find anything) with the information I'm looking for and/or more general information on the unlocking/signing process, I'd love to read it - I just haven't found anything like that so far.
Bump
I've recently picked one of these up and I have to say it's a great tablet for the price. However, I found that there's not a lot of support for this tablet as of yet. After rooting and customizing it, I'd accidentally screwed up the install and am now trying to find a way to flash it back to stock.
Is there anyway to fix this since there doesn't seem to be any stock files or custom ROMs available? I downloaded the firmware off of the official site, but have unsuccessfully flashed it using their tool.
Any help would be appreciated.
I don't think E-Fun/Nextbook has any firmware on their site for the Ares 8. I just looked and all I see are files for the Nextbook 7 and Nextbook 8--these are different models than the Ares 8. I have to assume that you didn't make a nandroid backup immediately after you rooted it and installed TWRP? Anyone else reading this would be wise to not repeat that error.
I wish I could offer some actual help, but unfortunately I cannot. Like you, I'm really hoping that some kind hearted dev sees fit to release a ROM for this tablet. It sure has potential.
Oops, you're right. I read the wrong firmware. I guess for now I'll try and install Ubuntu, etc. until a rom comes out. =/
I am officially stuck in bootloop after editing the build prop; trying to get split screen ability. I do not have a back up, but truly I thought I did. It is rooted but no custom recovery installed. I have tried to reset to factory but it does nothing. The brand is Marozi the model is C8000 OTA. It had Android 5.1.1 can anyone help me? If there are any downloadable Android images or Android OTA files that I can use to flash the Android image back on the phone since I do have root privileges would help. I am completely okay doing a clean install and wiping the phone. I can absolutely even flash a ROM that is compatible with my phone and go that route as well. At this point I am willing to try anything and do everything to have it working again. Personal life is very unsafe with two kids and I need a working phone and honestly cannot afford to buy a new one. A case of beer to anyone who can help me.
Thank you!
Candace
Hello there, sorry for posting, this is literally my last resort.
So, here's the whole story. In my attempts to install a custom recovery mode(first TWRP) then I tried to follow this guide: Link is here of xda forum. So, my phone runs Fastboot and doesn't really have any stock recovery (just a factory settings window, which is now gone as well). So apparently after I entered these two commands into adb
fastboot oem unlock
fastboot format userdata
Click to expand...
Click to collapse
The first command unlocks the boot-loader and I thought that the second command would erase userdata, which is just photos and files, but apparently that second command has erased the whole rom + the factory settings window, that was on the phone.
So that's basically the story, now I am searching for a Stock ROM of the Flycat Optimum 5501, Android 5.1.
My phone is:
Flycat optimum 5501
Was running Android 5.1
If any information is required, I will provide. Please help and thank you for reading!
Alright development update. I've did like hell of a lot of digging, until it hit me to check the official Flycat website, so I went back and forth through the whole website right? And bam, I literally found 2 STOCK ROMS by going to this link.
I am still currently looking into ways to how to install this rom. If anyone could give advice onto how to install it using Fastboot, I would be thankful!
Update: So I found out that an application "Smart phone Flash tool" can flash your whole phone if you accidentally ****ed up. So I went to watch a few tutorials in youtube about that application and I managed to unbrick my phone. It works as it worked at the start. Welp I managed to fix it with pure research and dedication to this **** (I gotta get some beer)
At any case, for those of you who have the same phone and run into the problem. I hope that my updates will help ya. Sorry for the constant posting, my problem is fixed ^^
I do still wanna find a custom recovery image, that would work on this phone, so if anyone finds a way, please comment!