I used the afterota tool to install ics bootloader and twrp 2.1.3 recovery. I have tried flashing Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT.zip. It says it flashed but when I try to boot it never gets past the screen that says acer. Can anyone point me to a guide that can help me get it booting properly?
lawtalking said:
I used the afterota tool to install ics bootloader and twrp 2.1.3 recovery. I have tried flashing Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT.zip. It says it flashed but when I try to boot it never gets past the screen that says acer. Can anyone point me to a guide that can help me get it booting properly?
Click to expand...
Click to collapse
Found the problem. Although I thought I flashed the ICS bootloader, I must have still been on the HC bootloader. I reflashed the ROM along with the HC kernel, and it booted up.
Related
I have installed the ICS V4 bootloader and everything is fine. (it has the big PASS thing). I can boot up to HC 3.2.1 fine as well.
However, when I go to press power+volume down, I get "booting from recovery kernal image" then it switches to a picture of the android with a caution sign.
Do I have to root my device and install CWM or something? (sorry I'm still quite noob at this, I haven't rooted yet). Didn't I already install this when I installed the bootloader?
Thanks in advance!
Booting stock HC and stock ICS after installation of ICS BL overwrites recovery.
Follow civatos guide for installing ICS BL V4:
http://forum.xda-developers.com/showthread.php?t=1622425
And do all the steps.
Greetings
edit: on Moscow's advice ;-)
HalloSpencer said:
Booting stock HC after installation of ICS BL overwrites recovery.
Follow civatos guide for installing ICS BL V4:
http://forum.xda-developers.com/showthread.php?t=1622425
And do all the steps.
Greetings
Click to expand...
Click to collapse
This includes Stock ICS Roms also
Thanks guys. I immediately booted to recovery after installing the bootloader. Now I have ICS running.
If I wanted to update to the V5 bootloader, could I do it without reinstalling my rom?
You guys are awesome
jgv115 said:
Thanks guys. I immediately booted to recovery after installing the bootloader. Now I have ICS running.
If I wanted to update to the V5 bootloader, could I do it without reinstalling my rom?
You guys are awesome
Click to expand...
Click to collapse
If I'm not mistaken, I believe you can put the v5 bootloader.blob in a flash.zip and flash through CWM. That's one method. This became available as of ver4.
The other would be to run the NVFlash again you used previously, and install only the bootloader (apx?). Your CWM and Rom should remain intact.
I use Blackthund3r's flash exe to install my .bin files. (gives some funny windows error but always completes) I just toss the new bootloader.bin in the same folder as the exe app. Also the latest recovery image. Do them both at the same time.
So basically 3 methods. Also, check your new UID number and make sure you convert it to SBK like you did the last time. ICS usually changes the UID number sometimes. I usually keep all UID's and SBK's written down.
Moscow Desire said:
If I'm not mistaken, I believe you can put the v5 bootloader.blob in a flash.zip and flash through CWM. That's one method. This became available as of ver4.
The other would be to run the NVFlash again you used previously, and install only the bootloader (apx?). Your CWM and Rom should remain intact.
I use Blackthund3r's flash exe to install my .bin files. (gives some funny windows error but always completes) I just toss the new bootloader.bin in the same folder as the exe app. Also the latest recovery image. Do them both at the same time.
So basically 3 methods. Also, check your new UID number and make sure you convert it to SBK like you did the last time. ICS usually changes the UID number sometimes. I usually keep all UID's and SBK's written down.
Click to expand...
Click to collapse
Can you pm me that windows error please? I think it's to do with my mode detection code being stopped abruptly but I want to have it fixed properly for v0.3.3
Sent from my Iconia A500 using Tapatalk 2
I read and re-read the development thread for AfterOTA and I found nothing on this problem. I will outlay the steps I took. I downloaded AfterOTA lite v1.7 and connected my tab to it and saved the txt file. (I can list the full output if needed) the Bootloader was as follows:
bootloader: 0.03.0X-HC
Android Build: FLEXREAPER RF1_rv1_Acer_AV041_A500_1.031_033_041.00_CUS_WW_GEN1
I booted into Recovery and found the version number.
My custom recovery: ClockworkMod Recovery v5.0.0.0(thor2002ro rev1.3.4)
I bought this from a friend and didn't do all the modding myself which I am new to the Iconia a500 (but not new to Rooting, Romming, Recovering) so I am a little in the dark on where to go from here.
I downloaded AfterOTA 1.7 (the Full version) and clicked on the "standard" tab and chose the install "bootloader ICS v 3.14.7 + recovery thor v1.7.3" and clicked the "for 50x"
It shut the tablet down said booting into APX, did the whole thing and at the end it said "complete, you can power down your tablet with the power button and boot back up"
I powered it down it booted up fine but when I reconnected it to afterOTA it dosent read the CPuid (it just says "0") and the bootloader space is blank.
Everything works, I can use it as I normally would but I want to install the new flexreaper and thought I might as well update the Bootloader and recovery to get up to current on everything. Thank you for any help you can give me in understanding what happened and what I may have done wrong. BTW I did disable all antivirus and UAC and rebooted before running AfterOTA.
You're probably ok. You just need to flash a "real" ICS rom like Flexreaper Extreme I would guess.
When you boot your tab, you should see some text in the left corner like "Skirlax_CZ's bootloader version xxxxxx" If you do, then bootloader is probably ok. Boot into your recovery and check your recovery version.
MD
I dont have anything come up when i boot other than a big white acer logo and then it does two smaller acer white logos side by side. Then it does the android boot animation. I booted into recovery and it is thor v5 not the one i had chosen in afterOTA. I just want to know what to do from here. Should i try again or use another method?
I just dont want to flash an ICS Rom without the ICS bootloader.and is there another way other than afterOTA to check the boot loader version?
york629 said:
I just dont want to flash an ICS Rom without the ICS bootloader.and is there another way other than afterOTA to check the boot loader version?
Click to expand...
Click to collapse
Well, after ota didn't work then. You should have seen the txt immediately on boot. (the split acer tells me it's a HC modified ICS kernel in the rom).
You could try manually flashing the bootloader with NVFlash.
My theory, is that you should install the OTA/Full version of ICS. This will install the stock bootloader, then, you can run the after OTA app. Reason being, is that my theory is that the real ICS bootloader creates something the HC BL doesn't. And when you try NVFlashing the unlocked bootloader, it just doesn't take. It's been happening several times recently.
Is there a forum guide on installing the OTA/full version of ICS? Would I basically bring it to stock bootloader and ROM then use AfterOTA to flash the new bootloader and recovery? Sorry for the n00bish questions, every device seems to use different methods and when I didn't start with the thing until after someone else did the initial stuff I dont want to mess it up, this is a really nice tablet. Thanks for the help, You guys are the best on here.
Yep, you are basically taking it back to stock then using afterOTA to install the new bootloaders but most importantly get root access and a new open recovery...
Is the best way to go stock by using afterOTA? Or should I just try a different method on the forums?
It clearly states on AfterOTA's first post that it does not work on custom roms and only the OTA so yes, download the ota ruu and install it. Then run afterota and you will be able to install a custom rom after that. Or use blackthunders apx tool to update the bootloader.
yes, that was an over sight on my part, I was excited to update everything so easily. where/what is the OTA RUU ? sorry to be a pain but if you could just point me to a forum guide on going completely stock I would appreciate it. I don't see anywhere to get the OTA update.zip file I need to flash, I found this here http://forum.xda-developers.com/showthread.php?t=1113878 is this the post I need? and do I need the update or the full package? does it matter if I use the honeycomb full package if I am just going to use afterOTA to install an ICS bootloader and recovery?
I'm trying to install jelly bean on my kindle fire but using KFU I've only managed firefirefire and clockworkrecovery.
I tried rooting using KFU to root but that doesn't work. Always gets stuck with the twrp.img error saying it's the wrong image (seems to be a common problem)
I've tried getting twrp installed using adb shell but when I get to the command to load the recovery image I get error; couldn't load recovery image. I thought maybe there was a problem so I tried loading the fff bootloader even though I already had it on my kf but it also returned with error: couldn't load image.
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
soupmagnet said:
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
Click to expand...
Click to collapse
The problem is getting root access. Most of the guides I've tried to follow require twrp installed to get into recovery. Without root I can't flash another rom.
I also already have FFF 1.4.
So I reverted back to stock and went through the manual process again and I was able to get it to work. When I was initially trying to flash twrp with the command line I copied pasted the name of the file without adding the file extension. Fixed that by adding .img and everything went through. Got Jellybean on here now and it's running great.
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
soupmagnet said:
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
Click to expand...
Click to collapse
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
hxu976 said:
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
Click to expand...
Click to collapse
That has nothing to do with "rooting". Most of the time it's caused by a bad download (always check MD5s) or not "wiping" correctly before installation.
I tried to flash a JB rom on my A500 with HC 3.2
Used AfterOta and choose the Standard Tab > Bootloader HC 3.01 + Recovery Thor 1.7.3
Went into recovery and flashed the JB rom, installation completed. Reboot, stuck at Acer logo
I could still boot into recovery, what should I do next?
Thank you
BaoQ said:
I tried to flash a JB rom on my A500 with HC 3.2
Used AfterOta and choose the Standard Tab > Bootloader HC 3.01 + Recovery Thor 1.7.3
Click to expand...
Click to collapse
You should have chosen the unlocked bootloader v3 & 1.7.3
Went into recovery and flashed the JB rom, installation completed. Reboot, stuck at Acer logo
I could still boot into recovery, what should I do next?
Thank you
Click to expand...
Click to collapse
You could try re-flashing the correct bootloader, not sure if it will work tho but no harm trying.
Failing that, use the manual nvflash method. You must have that unlocked bootloader to run any of the xda ics or jb custom roms
Sent from my GT-I9300 using Tapatalk 4
BaoQ said:
I tried to flash a JB rom on my A500 with HC 3.2
Used AfterOta and choose the Standard Tab > Bootloader HC 3.01 + Recovery Thor 1.7.3
Went into recovery and flashed the JB rom, installation completed. Reboot, stuck at Acer logo
I could still boot into recovery, what should I do next?
Thank you
Click to expand...
Click to collapse
Go to recovery, flash an hc rom.
After boot, get your uid number. Then nvflash the unlocked bootloader.
Recovery might show you your uid number also.
Thank you guys, I got it
Used Manual Nvflash to fix it
BaoQ said:
Thank you guys, I got it
Used Manual Nvflash to fix it
Click to expand...
Click to collapse
awsum, thanx 4 letting us know u got fixed!
could u plse add [SOLVED!!] to the title of your thread, just to help out others finding themselves in the same boat
cheers dibb
Hi all,
I got some strange problem:
I did an ODIN reinstall of complete OREO stock samsung ROM.
I swiped in twrp but i didnt want that so i reflashed twrp with odin.
Then i got a red screen while i wanted to enter TWRP. I retried flashing, no luck still a red screen. Also older versions.
I do however seem to be able to boot into samsung recovery mode.
I tried to flash twrp with adb. But my phone will not boot into Bootloader mode? It just restarts?
(as i understand, Bootloader mode is NOT download mode right?)
It is soft brick something?
Any help would be appriciated very much.
Thx!
Mrmoves
EDIT: I just found out im on Bootloader 3.
I have flashed the newest OREO a lot of times now with ODIN. Its works. Going into recovery works as well.
Still not able to boot into bootloader, or install TWRP for some reason?
EDIT2: I fixed it!. i flashed the newest OREO for the 5th time or smhting and for some reason i was also able to get TWRP on it again =)
Now rooted with Magisk all working =)
TOPIC CAN BE CLOSED