I followed guides (this guide) on this site to convert my HTC One Dev Edition --> Google Play Edition with OTAs.
This is what I did:
- The phone was already unlocked.
- I got S-OFF.
- I verified that my MID was correct and changed my CID to match the Google Play Edition phone.
- I installed TWRP Recovery and used it to wipe the phone.
- I flashed the "Pre Rooted 4.3 RUU Zip"
The phone is running well with 4.3 now.
What I need help with:
I don't plan on flashing ROMS in the future, I just want it to be a GPE with OTA updates.
My understanding is that flashing the RUU also installs the GPE stock recovery (overwriting TWRP), and the stock recovery has to be there in order to get OTAs. Is this right?
When I enter the bootloader and choose recovery, I see this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this normal?
Does it mean that the correct stock recovery is in place?
ggabriele3 said:
I followed guides (this guide) on this site to convert my HTC One Dev Edition --> Google Play Edition with OTAs.
This is what I did:
- The phone was already unlocked.
- I got S-OFF.
- I verified that my MID was correct and changed my CID to match the Google Play Edition phone.
- I installed TWRP Recovery and used it to wipe the phone.
- I flashed the "Pre Rooted 4.3 RUU Zip"
The phone is running well with 4.3 now.
What I need help with:
I don't plan on flashing ROMS in the future, I just want it to be a GPE with OTA updates.
My understanding is that flashing the RUU also installs the GPE stock recovery (overwriting TWRP), and the stock recovery has to be there in order to get OTAs. Is this right?
When I enter the bootloader and choose recovery, I see this screen:
Is this normal?
Does it mean that the correct stock recovery is in place?
Click to expand...
Click to collapse
Yes, that is absolutely normal, when you boot stock recovery, it's looking automatically in your file structure for something to flash. When it doesn't find anything, you get this screen. To get to recovery options just hold volume up and hit power, the screen will go grey and you'll see the recovery options.
Hope this helps.
Related
After managing to unlock via fake cid, installing twrp recovery, my attempt to install nj's Kangbang rom failed (something like com.android.core errors) Attempted Rancun Soff, made it partially through but my command window repeatedly froze at step where original RUU is installed.. (using win vista 32 bit) ..
Been going mad trying to fix this, and now can only gt to the bootloader screen- fastboot works, but get errors trying to flash any image- same with any attmpt to artificially place PJ53Img.zip (recovery, RUU, rom...) or any other file on external sd, then booting.
Essentially stuck with this screen (or Fastboot)....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
soccerfocus05 said:
After managing to unlock via fake cid, installing twrp recovery, my attempt to install nj's Kangbang rom failed (something like com.android.core errors) Attempted Rancun Soff, made it partially through but my command window repeatedly froze at step where original RUU is installed.. (using win vista 32 bit) ..
Been going mad trying to fix this, and now can only gt to the bootloader screen- fastboot works, but get errors trying to flash any image- same with any attmpt to artificially place PJ53Img.zip (recovery, RUU, rom...) or any other file on external sd, then booting.
Essentially stuck with this screen (or Fastboot)....
Click to expand...
Click to collapse
ukb is based off the old software, therefore you have to flash the boot.img of the old software via adb.nits has both te new and old boot images posted here somewhere.
unfortunately, at the moment i am unable to successfully flash anything via fastboot...no twrp, no stock recovery...
You said in the OP that you unlocked your bootloader. You'll need to re-lock if before the RUU will successfully install.
sorry, thought i posted this screenshot earlier- i am relocked but this is the only gui i can access
I know this seems obvious, but are you getting the stock image files from here: http://forum.xda-developers.com/showthread.php?t=1770978 ?
Ok so this may have been posted before but I've been searching and can't find anything.
So I got my note 2 when they released and I did the first "root" method available which I think was odin. Not really root with a custom recovery however I don't think. See the following screenshot to see what I'm currently running. Its been fine until now so I never re flashed anything or install twrp or anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lately its been running slow so I want to fully root and install something along the lines of the latest Clean Rom. I had cleanrom on my Rezound and I love his roms.
Only reason I'm making this thread is because I'm not sure where to start because I don't think I'm stock yet I'm not "really" rooted.
Dont want to mess up my device.
Thanks!!
ufvj217 said:
Ok so this may have been posted before but I've been searching and can't find anything.
So I got my note 2 when they released and I did the first "root" method available which I think was odin. Not really root with a custom recovery however I don't think. See the following screenshot to see what I'm currently running. Its been fine until now so I never re flashed anything or install twrp or anything.
Lately its been running slow so I want to fully root and install something along the lines of the latest Clean Rom. I had cleanrom on my Rezound and I love his roms.
Only reason I'm making this thread is because I'm not sure where to start because I don't think I'm stock yet I'm not "really" rooted.
Dont want to mess up my device.
Thanks!!
Click to expand...
Click to collapse
Sounds like you are rooted, but your bootloader is still locked. In order to flash ROMs on Verizon you will need to unlock the bootloader (unless you did that via Odin the first time around). From those screenshots you won't be able to tell if you have unlocked the bootloader...as far as I know the only want to check is to boot into recovery. If you see TWRP or CWM you are set...if you get the stock recovery you need to follow Adam Outler's original unlock method as you are on baseband VRALJB. To access recovery power off the device and then press volume up + power button + home button simultaneously. Whatever boots up will tell you what you need to know.
stary by reading the stickies.
Yea I believe I'm still on the stock recovery.
hi i managed to update my tab to the latest firmware 4.0.4 . Previously it was already rooted and TWRP installed. I was thinking of rooting and backing up this build so from romtoolbox i boot into recovery mode (thinking that i will be seeing TWRP) But when boot i was shown the folllowing picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
since all of my buttons are not working (hence the reason installing TWRP ) i was ok fine lets reboot it via adb. therefore i run adb reboot and yet it still boots back to the same screen . Thinking i need to reverting all of the changes via odin i tried reboot download also does not work. reboot-bootloader also does not work. apprently i am stuck at this screen.
Right now i only have access to adb and is there any way i can recover from this?
many thanks again
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Soryuu said:
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Click to expand...
Click to collapse
the thing is i only root and installed twrp for the sake of backing up since my daughter loves to install application. I've read about pushing / Installing application but that would requires root right? this is my command console like
Right now is there a way to force it to boot into download because thats the only way i see i can fix it (without using physical buttons)
Again many thanks for replying.
Hello. I own a kindle fire HDX 7 (Thor) with a bootloader installed, but can't install the new rom. I wipe first, then install the rom, and finally gapps. After resetting and pressing continue to skip the recovery, the screen just stays black until it fails and I reset my device back into recovery.
Anyone know what I may be missing?
Thanks!
Edit: the recovery installed is Safestrap 4.01 (TWRP v2.7.1.0). I'm kind of confused as to whether this is safestrap or trwp.
Safestrap isnt the same as TWRP, if you have Safetrap ,you are limited to bootloader locked ROM's like FireNexus KK, you need unlock the bootloader to get full TWRP recovery
Every single ROM needs a minimum recovery build installed to get flashed properly, if my memory dont fail, Marshmallow and Nougat ROM's, needs TWRP version 3.0 or newer ,otherwise thats why you cant install it.
If you have TWRP, you can upgrade using Flashify,start the system, downaload Flashify from Google Play, open it, and use recovery option to replace old TWRP, just grab the new TWRP (search in the forums the links) replace it and reboot, and its done
But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device
This is a TWRP recover screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this is Safestrap
Yousucks2 said:
Safestrap isnt the same as TWRP, if you have Safetrap ,you are limited to bootloader locked ROM's like FireNexus KK, you need unlock the bootloader to get full TWRP recovery
If the ROM have Marshmallow or Nougat core, you need a newer version of TWRP, version 3.0 or newer ,otherwise thats why you cant install it.
If you have TWRP you can upgrade using Flashify,start the system, downaload Flashify, open it, and open recovery option, just grab the new TWRP (search in the forums the links) replace it and reboot, and its done
But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device
Click to expand...
Click to collapse
Excellent response!
@leeismyname - I happen to be helping another member through unlocking the bootloader (here). Feel free to tag along. Just be sure to use the "Thor" (7" HDX) vs "Apollo" (8.9" HDX) files when installing the vulnerable aboot (bootloader) and TWRP. Ask questions in that thread as needed.
Thank you both for your timely and informative responses! From the pictures, I know I have safestrap. Time to piggy back off Davey's other thread!
Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection
foobar66 said:
Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I don't recommend using the Pixel Repair Tool unless absolutely necessary.
If you are trying to return your device to absolute stock, I recommend using the Android Flash Tool. You can choose which factory build to flash, whether to wipe the device, and whether to relock the bootloader.
aymuhamm said:
Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?
View attachment 5475895
Click to expand...
Click to collapse
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.
Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.
After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader.
VozerCozer said:
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.
Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.
After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader
Click to expand...
Click to collapse
This is why I like to recommend the Android Flash Tool - simply from a perspective of ease of use, and the fact it's practically impossible to get wrong; additionally, the user can elect to lock the bootloader during the process when choosing the flash options. This removes the need to do anything else manually; the tool takes care of the entire process.
It's also very useful for updates.