Database Info

Need some help flashing Clean Rom 5.1

I have downloaded CleanRom 5.1 from a long time ago, now the link is not up for that rom. The size is 598 mb.I have flashed this rom before but now I can't get it to flash. In recovery I have wiped, dalvic,cache, system, and factory. After I choose what to flash from Aroma it goes to flash a couple of seconds then goes to the other screen to finalize, but when going to reboot, I get "no OS , do you really want to reboot".
S-OFF
unlocked
on 2.20
Tried this with HBOOT 1.09 and now on HBOOT 1.14, I would redownload but the link is gone now , and I can't figure out how to get it to flash, luckily I do have a back up that works

Downgrade your recovery to twrp 2.3 bet you are using a 2.4 version
Sent from my HTC One X using Tapatalk 2

jerrycoffman45 said:
Downgrade your recovery to twrp 2.3 bet you are using a 2.4 version
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I had 2.4 downgraded to 2.3 but having troubles now. Seems Clean Rom 5.1 is the only one I have trouble with even on TWRP 2.3

Sorry maybe someone else will know what to do I am out of ideas
Sent from my HTC One X using Tapatalk 2

leesumm said:
I had 2.4 downgraded to 2.3 but having troubles now. Seems Clean Rom 5.1 is the only one I have trouble with even on TWRP 2.3
Click to expand...
Click to collapse
Don't know if you have the MD5: C8D3304C4120F5B0AEBE75BC6B4F733C But check that. If it doesnt match, lemme know and I think I have a copy of this rom to upload for you at home assuming Dev won't mind.
Also, after downgrading from twrp 2.4 to 2.3 did you do fastboot erase cache? Regardless I would recheck checksum twrp if you have the image saved or redownload and check checksum, reflash (fastboot flash recovery "recoveryname.img" (sans "") and then do fastboot erase cache.
Lemme know.

exad said:
Don't know if you have the MD5: C8D3304C4120F5B0AEBE75BC6B4F733C But check that. If it doesnt match, lemme know and I think I have a copy of this rom to upload for you at home assuming Dev won't mind.
Also, after downgrading from twrp 2.4 to 2.3 did you do fastboot erase cache? Regardless I would recheck checksum twrp if you have the image saved or redownload and check checksum, reflash (fastboot flash recovery "recoveryname.img" (sans "") and then do fastboot erase cache.
Lemme know.
Click to expand...
Click to collapse
NO. I don't have the md5 for that rom. I downloaded it some time ago and sitting idle in the folder on the PC. I was messing around in places that I shouldn't have been and somehow things got deleted. My backup of that rom I had flashed works fine. Its when I go to flash the rom from zip that I have a problem.

I am really scratching my head now!!!
The same rom, the same zip that I have been asking about that wouldn't flash, now flashes fine and installs. I was using TWRP 2.4.1 for a long time and was having a little problems with different things and trying to flash some add ons to the rom playing with it. Reading some of the posts I read some were having problems with TWRP above 2.3 so I downgraded the recovery,thats when I couldn't flash the zip I had of Clean Rom 5.1. So, for the fun of it, I upgraded back to TWRP 2.4.1 and tried to reflash the same zip package, everything works fine now it flashed and booted. Got me scratching my head ...

leesumm said:
The same rom, the same zip that I have been asking about that wouldn't flash, now flashes fine and installs. I was using TWRP 2.4.1 for a long time and was having a little problems with different things and trying to flash some add ons to the rom playing with it. Reading some of the posts I read some were having problems with TWRP above 2.3 so I downgraded the recovery,thats when I couldn't flash the zip I had of Clean Rom 5.1. So, for the fun of it, I upgraded back to TWRP 2.4.1 and tried to reflash the same zip package, everything works fine now it flashed and booted. Got me scratching my head ...
Click to expand...
Click to collapse
Makes sense to me, sounds like you didn't do fastboot erase cache after switching recoveries. When you flash a new recovery you need to do fastboot erase cache.

Took 4.4.3 OTA with custom recovery >.<

Hello experts,
As the title states I ignorantly took the OTA 4.4.3 with TWRP installed. After downloading the phone asked if I wanted to install the new firmware. I clicked yes and my phone went right into recovery. I tried to nan droid back to Venom 1.8 and It just stuck on the splash screen. I tried multiple venom rom nan droids and none would boot.
I was able to nan droid back to my stock back up (not stock recovery but everything else). I flashed the stock recovery through adb/fastboot and am now trying the OTA again. I assume the OTA should work now ( unless I am missing something ?).
Once the OTA takes, assuming it does, should I be able to restore back to venom ? What was preventing the restore from working originally?
Thank you so much for any help you can offer.
-Tony

Trantzz said:
Hello experts,
As the title states I ignorantly took the OTA 4.4.3 with TWRP installed. After downloading the phone asked if I wanted to install the new firmware. I clicked yes and my phone went right into recovery. I tried to nan droid back to Venom 1.8 and It just stuck on the splash screen. I tried multiple venom rom nan droids and none would boot.
I was able to nan droid back to my stock back up (not stock recovery but everything else). I flashed the stock recovery through adb/fastboot and am now trying the OTA again. I assume the OTA should work now ( unless I am missing something ?).
Once the OTA takes, assuming it does, should I be able to restore back to venom ? What was preventing the restore from working originally?
Thank you so much for any help you can offer.
-Tony
Click to expand...
Click to collapse
Twrp recovery doesn't flash firmware. If all you want is the updated firmware, go to tigerstown's thread and flash the firmware only zip and stay on venom the whole time.

College assisten
dottat said:
Twrp recovery doesn't flash firmware. If all you want is the updated firmware, go to tigerstown's thread and flash the firmware only zip and stay on venom the whole time.
Click to expand...
Click to collapse
Yes, going forward I will install the firmware via fast boot . Since I had a stock backup ( so I thought) I wanted to try it this way.
Everything is working as intended now. Once I flashed the stock recovery the phone updated and I was able to restore Venom 1.8.
Thanks for your input.
-T

[q]help with system img

I have the Nvidia Shield 16 Gig Wifi tablet and Ive only had it for about 2 months. I wanted to unroot and completely go back to out of the box settings. I flashed the stock recovery, and boot. When i flash system.img it says insufficient space. Im really freaking out over this. I now have CWM running as recovery, but im stuck in a bootloop/softbrick. Ive had this with other tablets before but it was fixable, Im stumped with this one. I really need help here. Please and thank you for help, I need it ASAP.

ProSniper54 said:
I have the Nvidia Shield 16 Gig Wifi tablet and Ive only had it for about 2 months. I wanted to unroot and completely go back to out of the box settings. I flashed the stock recovery, and boot. When i flash system.img it says insufficient space. Im really freaking out over this. I now have CWM running as recovery, but im stuck in a bootloop/softbrick. Ive had this with other tablets before but it was fixable, Im stumped with this one. I really need help here. Please and thank you for help, I need it ASAP.
Click to expand...
Click to collapse
So, basically you left your shield tablet without a rom installed? If you have CWM recovery, you could flash a Full OTA found here http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
It happened to me to. So I downloaded a Philz built in Jan (I googled it)**** and I flashed the full 2.1 ota.
You could flash the TWRP 2.8.5.0 found here:http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90 and then flash the full ota.
Then, Im thinking, you could flash stock recovery. I'd recommend flashing TWRP though, I had a problem with CWM and I could not flash full 2.1 OTA with it.
PS: Did you try wiping system from CWM and then flashing system with fastboot?
****EDIT: I found the Philz I used: https://goo.im/devs/playground/shieldtablet/Philz_Touch-01-02-2015_14.18-TN8-WiFi.zip
but Ive moved forward to TWRP since I couldn't make nandroid backups with it.

NaminatoR1254jaime.sier said:
So, basically you left your shield tablet without a rom installed? If you have CWM recovery, you could flash a Full OTA found here http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
It happened to me to. So I downloaded a Philz built in Jan (I googled it)**** and I flashed the full 2.1 ota.
You could flash the TWRP 2.8.5.0 found here:http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90 and then flash the full ota.
Then, Im thinking, you could flash stock recovery. I'd recommend flashing TWRP though, I had a problem with CWM and I could not flash full 2.1 OTA with it.
PS: Did you try wiping system from CWM and then flashing system with fastboot?
****EDIT: I found the Philz I used: https://goo.im/devs/playground/shieldtablet/Philz_Touch-01-02-2015_14.18-TN8-WiFi.zip
but Ive moved forward to TWRP since I couldn't make nandroid backups with it.
Click to expand...
Click to collapse
Okay I have to thank you a ton for getting my tablet working again. Only problem now, I cant system update anymore, I get an android guy with a red warning sign in him. Any suggestions?

ProSniper54 said:
Okay I have to thank you a ton for getting my tablet working again. Only problem now, I cant system update anymore, I get an android guy with a red warning sign in him. Any suggestions?
Click to expand...
Click to collapse
Probably because you have custom recovery still or you are rooted.
The android red guy happens bc you are rooted (it'll happen even if you have stock recovery).
To system update, you have to be without custom recovery AND unrooted.
EDIT: Im theoretically speaking. I am rooted, therefore, I dont update via OTA.

i tried to recover to factory but i am stuck at system.img which dun seem to be copying into my tablet i manage to flash twrp in and wat else can i do to make it working again?
thanks

Custom ROM Issue... Stuck Booting...

Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!

Assuming you are trying to flash MM custom roms: You need the MM bootloader.

edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?

TWRP is a recovery. A bootloader is a bootloader.

This is covered in every rom thread that updated from L to M.

lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?

Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for

edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks

Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.

MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please

Update Build W/O a Computer

Ok, let me start by saying that I'm fully capable of updating my phone with a computer, I'm just hoping there is a better way. So far every time I've downloaded a new firmware, update the flash-all.bat and run it, something will fail towards the end of the update and the only way I've been able to successfully update is by using one of those tool kits (forget which one, it's on my computer). I'm not that concerned about all of that with this thread. I'm wondering if there is a way to do it without a PC.
I'm on NMF26O (root, ElementalX, etc) and tried flashing Pure Nexus over the weekend. Since it's based on NMF26V, I kept receiving an error on boot about updating my vendor.img. So I downloaded that firmware, extracted it, and flashed the vendor.img in TWRP. That led to a plethora of other issues that I couldn't resolve by flashing the boot.img, reflashing the rom, ect. Several hours later I ended up flashing the boot.img and vendor.img for NMF26O, restoring my backup, re-installing Elemental, and rooting again.
Since these updates will be coming out every month, and roms will always be based on the latest update, I feel like I'll be pulling out the computer every month, downloading the updates, modifying the flash-all.bat, and running it through the tool, just to be able to update my rom. The first time I forget to update flash-all.bat, I'll lose the 60+ GB's I keep in internal storage. There has to be an easier way. TWRP is capable of flashing images. Has anyone been able to update without using a computer? I don't care if my radio is out dated, or something is mismatched as long as my phone works as intended.
Sent from my Pixel using Tapatalk

Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though

aholeinthewor1d said:
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
Click to expand...
Click to collapse
I'm on NMF26O. What's the difference between it and NMF26U and why would the vendor image from NMF26V work with NMF26U but not NMF26O?
Seems like all you would need is the /system from the rom, the vendor image, and maybe the boot image (or a custom kernel). I think I'm missing something here.
Sent from my Pixel using Tapatalk

If you install PN its based on NMF26V. So unless you are already on that then you would need to flash the ROM, reboot back to recovery, then flash the NMF26V vendor image.

I'll play devil's advocate here... Yeah there is an easier way, use your Pixel stock and take OTA's. Enjoy a phone that always works, with or without a laptop!
I understand my audience and realize this isn't a popular mantra here but I felt exactly like you did with my 6p and vendor images. I got to the point where I sacrifice root now just for my own sanity. My phone works for me, not the other way around.

What I do is side load the full OTA ( which you can get from the same place you get the factory images ). I only use the fastboot boot version of TWRP so that my stock recovery stays in place. Then all you have to do is boot into the stock recovery, adb side load the OTA file and re root. Then you're fully up to date without worries of your data being wiped :laugh:!
( Although if you look in the flash fire thread from Chainfire, he's working on a version that will let rooted pixels flash otas like normal ones :fingers-crossed: )

I think you guys are missing the point. I have no desire to ever be stock, which rules out the possibility for an OTA in any form.
What I'm trying to figure out is exactly what is necessary to make a custom rom (based on the latest OTA), work if flashed over an older build, without first somehow applying the full OTA. Or is it impossible?
On just about every other phone I've owned, we could piecemeal the files needed for minor updates, along with a custom rom. The only time we'd have to flash a full update is for major updates ( 4 to 5 to 6, etc).
Sent from my Pixel using Tapatalk

Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Sent from my Pixel using Tapatalk

joshw0000 said:
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Click to expand...
Click to collapse
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU

aholeinthewor1d said:
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
Click to expand...
Click to collapse
I've done it several times tonight. Went from O to U to V, flashed Pure Nexus, screwed up the rom, restored to O, then O flashed back to U and V.
Just flash it like a rom in TWRP RC1. Make sure you flash TWRP again before rebooting if you want to keep it.
Sent from my Pixel using Tapatalk