Database Develop

Lost root after an autoupdate

I've just updated my G1 to ADP 1.1 with help from the post "How-to- Root, Hack, and Flashing your G1/Dream Read first!!".
Everything worked perfectly, auto-rotate, multitouch and everything. But suddenly a pop-up asked me to update 1/2 updates. I agreed, and no problems afterwords. But after a while update 2/2 came, and after that I lost root access and the extra functions.
What did I do wrong? Shouldn't I agree to these updates? And do I have to go through the procedure "How-to- Root, Hack, and Flashing your G1/Dream Read first!!" all over again?

ampliz said:
What did I do wrong?
Click to expand...
Click to collapse
You accepted an OTA update.

hmmm.... new update???? what one? whats new? firmware #?

I don't know whats new, just that I lost all the good stuff..
{
"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 the information you were looking for?

Strange.... it appears you have the JF build and a new kernal??? I'm on RC33 but my kernal is 2.6.25-01843-gfea26b0
EDIT: After looking into your kernal, it appears you simply have the ADP1 official build. Time to start over with flashing the NBH

U didnt lost root, have same firmware, just JF stuff is gone, just download ADP1.1h again rename it as update.zip und flash ist again...

McLin said:
U didnt lost root
Click to expand...
Click to collapse
He's right. HTC/Google are now sending out OTAs for ADP1 signed with the test keys. These updates will not take your root away, but you will occasionally have your /system normalized to the "canonical" ADP1 build (meaning a loss of the JF components, among things). Two easy solutions:
1. Install JF RCxx build.
-or-
2. Create your own crypto keys and replace the test keys with em.

Thanks for all the help!
I'm not so into making stuff myself to this device jet, making my own crypto keys, so the easiest solution for me is to repeat the last step in the procedure and flash ADP 1.1?
And not agree to any auto-updates in the future?

ADP Image from JF will still have enabled OTA cos you dont loose your root, by rc RF firmware its disabled, cos tmob will kill you root...
So ignore the update message, or build own keys...
I did install the original holiday update, and customie it to my stuff what I need... is another possibility

ampliz said:
Thanks for all the help!
I'm not so into making stuff myself to this device jet, making my own crypto keys, so the easiest solution for me is to repeat the last step in the procedure and flash ADP 1.1?
And not agree to any auto-updates in the future?
Click to expand...
Click to collapse
I can almost assure you that one day you will accidentally click Accept on an update dialog. I can't be sure if its the same as with the G1, but on the G1 update dialogs will keep popping up occasionally until you accept. At some point also, the update manager can be instructed to perform the update silently without your permission (no anecdotal cases of this occurring but the code is there to do it).
If you don't care about branding, the easiest way is simply to flash a JF RCxx build. The only thing that kind of irritates me about that solution is that every time the update manager pings the OTA server, it sends your imei in addition to the fingerprint.

So if I flash the phone to RC33 instead of ADP1.1 I wont have the problem with the update dialog? And still have root with possibility to auto-rotate, multitouch and use the phone as a wireless router for Internet access?

ampliz said:
So if I flash the phone to RC33 instead of ADP1.1 I wont have the problem with the update dialog? And still have root with possibility to auto-rotate, multitouch and use the phone as a wireless router for Internet access?
Click to expand...
Click to collapse
I have RC33 and have all of the above

HI, I'm posting in this thread because I see my problem is related to the one solved here, in fact I did update the phone from the version this user had:
I received yesterday a G1 I bought on eBay. When I received it I saw it was a Dev Phone 1 just like the one described in htc.com under the adp entry (sorry no external links):
In the terminal application I downloaded, the "su" command answered "#"
"about phone" said:
Model number: Android Dev Phone 1
firmware 1.1
Kernel 2.6.25-01845-g85d4f0d [email protected]#27
Baseband version: 62.33.20.08U_1.22.14.11
Build number: holiday_devphone-userdebug 1.1 UNLOCKED 130444 test-keys
I configured the internet access (spanish operator Movistar - phone is unlocked), a couple of minutes later a message tells me there is a new version of the system
Today checking "System Updates" I see a 40 something mb file with an update. I run it (I know - noob )
I'm no loger root, "su" command gives "su: permission denied" message
The new "about phone" says
Model number: Android Dev Phone 1
Firmware version 1.6
Baseband 62.505.20.17U_2.22.19.26I
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Build number DRC83
If I turn the phone on using power + back or power + camera I get a rainbow-like screen saying:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial 0
There's not much info about this version, maybe somebody could tell me what tutorial to follow in order to get root privileges again
Regards!

Do you have recovery tools like Amon RA,or cyanogen recovery ?
If you do, Can you go to console in recovery mod ?
If everything ok than the problem is only several file on your linux has false permission setting,
In your recovery console try:
chmod 6755 /system/bin/su
Or using adb
adb remount
adb shell
chmod 6755 /system/bin/su
Sent from my HTC Dream using XDA App

I had nothing installed as far as I know, can these recovery tools be installed now (without root privileges)?

Search the cyanogenmod wiki on the rooting process, which you need to do from the beginning.

cloverdale said:
Search the cyanogenmod wiki on the rooting process, which you need to do from the beginning.
Click to expand...
Click to collapse
As I am not root I have to use the G1 Dream tutorial, so I need to downgrade to RC29 (US) or RC7 (Europe).
I bought my phone on eBay from a Spanish guy but it is an Android dev phone 1. Should I use RC29 or RC7?

Moved to the Q&A section

[q] bricked?! Please someone help!

Hi all! I registerd now on forum but i'm an old noob reader of the forum. I
I bought Captivate(AT&T) on ebay and had Froyo 2.2 installed. I tryed to flash and root it to CYNOGENMOD with this GUIDE: wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
I did everything as written on thad guide but the phone continued to reboot and reboot and reboot. Now I don't even know what have I done but the phone starts with AT&T LOGO and than blocks with Samsung SGH i897 LOGO.
When i push volume buttons and start button it goes on CLOCKWORKMODRECOVERY.
Anyone can help me? I think i'm in big problem isn'it? PLEASE SOMEONE HELP!
(sorry for bad english)

alexmr89 said:
Hi all! I registerd now on forum but i'm an old noob reader of the forum. I
I bought Captivate(AT&T) on ebay and had Froyo 2.2 installed. I tryed to flash and root it to CYNOGENMOD with this GUIDE: wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
I did everything as written on thad guide but the phone continued to reboot and reboot and reboot. Now I don't even know what have I done but the phone starts with AT&T LOGO and than blocks with Samsung SGH i897 LOGO.
When i push volume buttons and start button it goes on CLOCKWORKMODRECOVERY.
Anyone can help me? I think i'm in big problem isn'it? PLEASE SOMEONE HELP!
(sorry for bad english)
Click to expand...
Click to collapse
Boot loop often happens and means you can't boot into the rom....it's called soft bricked. If you have recovery and download mode still active your safe.
1-Did you check you got the right files ?
2-Did you check the md5sum of the files (if available) to make sure your download is not corrupted.
3-Did you download and flash the proper cwm and/or kernel
4-You missed something in the process. (Recheck #[email protected])

silvertag said:
Boot loop often happens and means you can't boot into the rom....it's called soft bricked. If you have recovery and download mode still active your safe.
1-Did you check you got the right files ?
2-Did you check the md5sum of the files (if available) to make sure your download is not corrupted.
3-Did you download and flash the proper cwm and/or kernel
4-You missed something in the process. (Recheck #[email protected])
Click to expand...
Click to collapse
Hi thank you very much for answering. I managed to restart it by flashing a new rom downloaded online, a Froyo 2.2. As I am a little idiot if I write down infos about my firmware would you gently link me to a guide or tell me what should I do to upgrade in order do not do any mistake again? Anyway phone is from At&T but I'd like to unlock operator in order tu use my Italian sim.(before i screwed it up it was unlocked, as i bought it USED from ebay.)
Anyway these are the infos:
Firmware version 2.2
Baseband version I897UCJI6
Kernel version [email protected] #1
Build number:Froyo.UCJI6.
THANK YOU VERY MUCH. Hope to hear from you

PS: I used this to restore it I897UCJI6-OCD-REV02-Low-designgears.exe and ODIN, if this has any importance!

It should be posted in the OP or there should be a link to sufficient installation instructions in the OP of whatever Rom you would like to flash.
And no need to start a thread in the General and same exact thread in Q & A.
NO need to double post.
Help will be given even with one thread started.

Ok i won't crosspost, I did it because I really need help. Anyway my question.is: now that i have installed this 2.2froyo rom,as i don't know if phone is rooted or not CAN I install a superoneclick 2.3 gingerbread or should i do something first. Will this also remove sim operator lock? Please someone answer

Thanks everybody for help!

If u have root then u should have the "Superuser app"
{
"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"
}
or View attachment 854464, but Not this in ur app drawer. Or download a free app that requires root and test and see that way.
To go to a Gingerbread Rom from the Froyo 2.2 that u currently are running, u can use one of the One Clicks GB with Bootloaders in the Stickied One Click Thread in the Development Forum.
You have to have the GB Bootloaders in order to run a Gingerbread Rom, but once u have the Bootloaders there is not any need in flashing any bootloaders in the future, because the GB Bootloaders are backwards compatible.
There is risk in flashing bootloaders, so be sure u have a good micro usb to usb cable connection, preferably use a laptop so u don't loose power mid flash, remove all babies, animals, etc. from the room, so the cable does not get "accidentally" yanked during the flash.
Be sure u know what u r doing and then proceed.

How to fix my phone after breaking kernel (SM-G900A)

Hi! I have a Galaxy S5 G900A (AT&T), Which I wanted to change to a stock Galaxy S5 ROM, to get rid of all those AT&T apps that no-one uses. So I searched it up! Long story short, I found out that AT&T locked the bootloader and I can't do anything about it. Then I found this post to root my phone: http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299 . Then I just realized how I wanted root, so I did every thing they said, turned off reactivation lock, installed towelroot, and then flashed the file they said (G900A_ND3_Stock_Kernel) with Odin. After that, My phone just showed the Galaxy S5 logo for a minute like it's booting for the first time, and then it restarted to recovery (stock recovery). I clicked on reboot device in the recovery mode, and it just did the same. Afterwards, I tried to flash the G900A_Downgrade_to_NCE.tar file to go back to normal. Flashed it, and it said "firmware encountered an issue". I went to kies but it didn't see the device. Then I saw this video: https://www.youtube.com/watch?v=Jfgq6bYfKLg . It had a "All recover Samsung.tar" file which should be flashed with Odin. And, I flashed it in odin. Odin said fail but it went back to the state when it was rebooting to recovery. I tried downloading so many AT&T ROMs and flash it but all say "Fail(auth)!" in odin. Any help? Thanks.

Hope this helps, just ask I will help you further if I can.
I did this too. It's a noob mistake. But from what I understand there is still no way to root Galaxy S5 SM-G900A after the 5.0 Lollypop update. This has to do with the bootloader being locked and not enough dev support on these now considered too old phones to be worth their time.
It took me 3 months to fix it and basically from what I gathered, from you, using the same method. Shoot in the Dark Flashing.
{
"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"
}
Just keep flashing **** and hope it works. LOL. It can't get any worse, right? After three moths of trial and error Flashing and just a LITTLE wiser in these areas, I think I might be able to help you. You need to Flash something at least 5.0+. Nothing below this will work and will always get "Auth Fail!". That is your locked bootloader preventing you from downgrading and rerooting and reupgrading with an already unlock, root access, stock Rom.
This is the one I used to finally unbrick my phone:
Link it was posted at: http://forum.xda-developers.com/att-galaxy-s5/help/g900aucu4coi5-file-t3231450
Link to Download: 5.1.1 OI5 https://drive.google.com/file/d/0B11_scgy1qonMW45T0lRbXQ3ZHM/view
But any of these should work...
5.1 PA2 http://forum.xda-developers.com/att...w-to-update-to-g900aoi5-5-1-unrooted-t3235774
6.0.1 PH2 http://forum.xda-developers.com/att-galaxy-s5/general/g900a-mm-odin-package-g900aucu4dph2-t3477515
6.0.1 PH4 http://forum.xda-developers.com/att-galaxy-s5/general/galaxy-s5-android-version-6-0-1-t3419016
P.S. I was on KitKat before all the above. My biggest mistake was just Flashing random stuff. I inadvertently flashed a lollypop kernel and that is what forced me into an update I could not get out of. So no more root access for me. Lesson learned!
Oh and btw, Hello this is my first post. Never even saw a need to register an account until after be a reader for at least 5 months. The POWER of SEARCH. I did what 5 cell phone repair shops could not. Unbrick my Galaxy S5. All with the resources of this amazing forums.

Android Pay - MIUI 8.2.3.0 (MAHCNDL) | Chinese Stable ROM

Seems like Android Pay does not recognise the latest system update as an official ROM, after installing Android pay and giving all the permissions:
Android Pay can't be used on this device. This may be because your device is rooted, has an unlocked bootloader, or is running a custom ROM. As a result, Google can't confirm that your device meets Android Pay's security standards.
Click to expand...
Click to collapse
I inadvertently ran this update after purchasing the phone 2 days ago, didn't unlock the bootloader (though applied for it) and of course, haven't rooted.
I factory reset twice and still got the same. Looking forward to unlocking the bootloader so I can downgrade to the older ROM or even go on the global one (since I saw in another thread Android Pay's working on the latest global ROM V8.2.1.0.MAHMIDL, and the latest downloadable Chinese stable Rom V8.2.2.0.MAHCNDL)
Anyone updated and experience the same issue? And as I'm a newb in all of this, must I unlock the bootloader in order to downgrade?

Tried to get it to work, this time through using recovery flash (without need to unlock the bootloader and what not). Here's how I finally got Android Pay to work, and also got myself on Global Rom (lovin' it)
Prerequisite: Download the latest stable ROM file here to PC
1. Download the Chinese version of the Xiaomi Mi PC Suite and run it
2. Plug in your phone to PC and boot into recovery mode (push both volume up button + power button together until your phone reboots)
3. Allow driver to install, if you're in recovery mode, a prompt will come up. If not don't panic, read step 4. Otherwise go to Step 5.
4. If the PC Suite does nothing even if you push the big orange button on the right to connect (apparently they haven't upgraded the software to support Android 6.0 yet -_-"), click this button show below
{
"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 select the button with the words "Recovery" in it, it will prompt you to reboot your phone into recovery mode (push both volume up button + power button together until your phone reboots).
5. Select the ROM you pre-downloaded on your PC and let it run.
6. The PC Suite will look like it hits some error and on desktop the progress remains at 0% but somehow things are churning on your phone as you can see "MIUI update" and a progress bar below.
7. Let it run its course and allow the phone to reboot
8. Voilà, your phone is now in Global ROM
And Android Pay now works, hoorah!!!

Great guide, thanks a lot! I've got the sister phone to this one, the Xiaomi Mi Note 2... and my Android pay was not working with 8.3.2 global.. But now it is.. I will post a guide elsewhere as to how I had to fix it...

THIS is a DANGEROUS post, it may work - or like in my case it will start for just a moment then stop [causing a factory reset to occur] without updating. Make sure you have your mi account login and pass ready when it comes back up - or your locked out of the device setup.
Due to frustration caused by trying this post I ended up unlocking / rooting the device. It was easier than I thought it would be, flashed global fine from there and updated to 8.2.4.0 just fine OTA. Have gone on too work on other things I had decided not to due because I hadn't decided to root the device. So I guess there was a silver lining to this.

Lastest Version of Nougat For EVA-L09 UK Version

Until i looked on here today I wasnt aware there was actually an update for the huawei p9 as i the phones 'Check up update' would always tell me there was no new version. I have the P9 EVA-L09 UK version and am currently on EMUI Ver 4.1.1 and Android version 6.0. What is the latest update i can install on this phone please and will i lose all the data on my phone?

Depends on your build number. If it's C432 you should be able to update to Nougat. If not you will need to follow the debrand guide found on this forum.

My build number is EVA-L09C432B182, which is the correct version right? I just tried updating to B386 from this guide here...
http://www.stechguide.com/download-huawei-p9-b386-nougat-update/
but i get an error message saying that the update.app is the wrong version, do i need an early version of the Nougat FW??

It's a minefield. Some work some don't. I'd try an earlier build b360 or b361 maybe. You could also try using the Huawei updater guides are on here.

hmm tried version B360 and it gets to about 39% installer and then gives me a 'Software Install Failed' message. Do i need an even older version of the Nougat FW?

That's the oldest as far as I know. Did you try with 3 button or hidden update menu method.

nah i used the phone keypad code method. I have just unlocked my bootloader and installed TWRP, can i update it via TWRP safely?

Hmm well ive updated to Nougat but something doesnt seem to be right alot of the programs are missing and now im unable to get TWRP to load and just seems to load Huawei eRecovery when i press the volume up and power button on turn the system on. How do i got about getting the phone back to stock (bootloader relocked, un rooted, twrp uninstalled and back on Android Marshmellow 6.0)?? so i can start again?

Look for the b136 rom. I believe that fixes a lot of issues for people. Most of this is on the debrand guide. Have a good read of that thread.

wards5150 said:
Look for the b136 rom. I believe that fixes a lot of issues for people. Most of this is on the debrand guide. Have a good read of that thread.
Click to expand...
Click to collapse
Ok thanks i just posted a new thread as i now seem to be stuck on a 'this system is rebooting' screen (the warning screen you get that tles you the phone is unlocked) and the phone never actually boots anymore. Will me force flashing (Volume Up+Down+Power button) the b136 rom get me out of this predicament?

I've not had to do it myself but I have read that others have. Good luck. Shouldn't be this hard to update.

Hmm i dont even seem to be able to get the phone into the force update process (Volume UP+DOWN+Power) just hangs on the Huawei logo screen

Hmm i think the phone is bricked, im unable to get into the menu to update the Update.app file from the dload folder on the SD card, i cant even get the phone to switch off it just keeps restarting itself and freezing on the 'your device has been unlocked and cant be trusted' 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"
}
if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......
and if i hold down both the volume and power buttons i get this screen....
and not the firmware update screen i should be getting.
It has been suggested that i need to use DC Phoenix program to fix the phone but thats a paid method and dont really want to go that route if there is another way!??

Sorry to hear that mate. Good luck fixing it. It should not be this hard to update. For some it's easy for others it's a right pain. I'm sure there will be a way to sort it the hard bit will be finding it.