Database Develop

[Q] OTA update wont work?

Hi
newb here!
i have FRG33 build on my phone, and some time ago an OTA update came out that i couldn't install (i get "failed to verify whole-file signature" "signature verification failed" errors). i'm guessing the update is the 2.2.1 release - so how can i install it? i figure there's something i can drop on the sd card and install from there but i don't know what to search for or why this error happens at all (and google has been exceedingly unhelpful)
any help?
thanks!

Is your phone completely stock? Unrooted, stock recovery, stock rom...?

erm.. how can i tell? <,<
i bought it from a friend
i'm pretty sure it's at least rooted though, whatever that means (sudo-like access to phone i guess?) since i have an app called superuser and i downloaded lamppu (led flash as flashlight) which apparently needs root access to work (and it works)
if you need me to paste certain things from settings/options, i can do that

lavalove said:
erm.. how can i tell? <,<
i bought it from a friend
i'm pretty sure it's at least rooted though, whatever that means (sudo-like access to phone i guess?) since i have an app called superuser and i downloaded lamppu (led flash as flashlight) which apparently needs root access to work (and it works)
if you need me to paste certain things from settings/options, i can do that
Click to expand...
Click to collapse
Your phone has an unlocked bootloader if there is a padlock symbol on the first screen when you boot up (the one with the static x).
You can see what recovery is on the phone if you press and hold the volume down button while powering the phone on. This will take you to the Fastboot screen, and you will use the volume down button again to scroll down and select "Recovery" and then press the power button. That will either get you into the stock Android recovery (which will pretty much just be a /!\ symbol) or a custom recovery (which should have a nice text-based menu with options and such).
You can find out information about your ROM by going to Settings --> About phone, and scrolling down the bottom. If you would, post the various version numbers and settings and such.
If you are running another other than the stock recovery and a stock ROM, no OTA update will install for you.

aha, good stuff
here's what i got:
unlocked padlock symbol on boot
my recovery menu is "clockworkmod recovery 2.5.0.7"
android ver:
2.2
baseband version:
32.36.00.28U_4.04.00.12_7
kernel:
2.6.32.9-27237-gbe746fb
[email protected] #1
build#
FRG33
so presumably no OTA updates
how do i get my updates then? (and stop the "you have an update, update now!" pop-up which pops up even during video playback.. i mean, really?)

If you want to get the automatic updates, you'll have to revert back to a stock ROM and a stock recovery. There should be instructions for that in one of the stickied threads.

well, i assume there's a way to update manually as well?
so i guess my question is
a) how do i know what's this OTA update (i.e. where i can find a link for it)
b) how do i install it manually?
and/or i guess more generally -- is there a general intro tutorial to tinkering with android phones that also explains terminology etc (for instance, you said i need a stock ROM, but from http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms, FRG33 is a stock ROM, so am i misunderstanding terminology here? i.e. difference between ROM & build?)
thanks btw, you've been really helpful

Answer: SEARCH.
There must be at least 100 threads on this very topic. To update, you're either going to have to flash a new rom, or revert back to the original shipping rom. Search or read the wiki on how to do either.

Or disable signature checking on CW recovery and OTA updates will install fine.

GldRush98 said:
Answer: SEARCH.
There must be at least 100 threads on this very topic. To update, you're either going to have to flash a new rom, or revert back to the original shipping rom. Search or read the wiki on how to do either.
Click to expand...
Click to collapse
i've tried searching but it's a little difficult when i don't know any related terminology (hence the request for an intro guide of sorts). it's not like i'm posting here without doing nothing else, but google queries like site:xda-developers.com nexus one ota error frg33 for example didn't yield much. i did find a how-to-get-back-to-stock tutorial here but i am still looking for a tutorial to understand that tutorial as i have no experience with adb or fastboot, etc. (not to mention its last updated date is a year ago (although last edited date is fairly recent.. but i'm still wary) i'm learning though.
Rusty! said:
Or disable signature checking on CW recovery and OTA updates will install fine.
Click to expand...
Click to collapse
is there any risk to doing this? if not, this seems to be the simplest option so far, but doesn't a failed signature check usually signal an incompatibility/corruption?
thanks again for your help guys!

The reason it failed the check is because custom recoveries use test keys, and OTA updates use release keys. It's quite safe

If you poke around a little bit, you'll find stickies referencing you to the NexusOne wiki. The following are two guides on adb listed there:
[Newbie Guide] adb/fastboot/bootloader/android 101
[GUIDE] ADB For Beginners (Setup, Use, and More!)

[Q] Need Help with cusotm recovery and root

I just bought the developer edition for verizon. I unlocked the bootloader successfully, i installed twrp is cmd and it said it installed successfully. I did not, however, open twrp immediately, which may be the problem. because if i go into download mode and click on recovery, nothing happens, my phone just goes black, like it powers off.
I tried opening cmd window again and installing again, only now the cmd window says the device is not connected, even though it is, or says it can't load the file. and ive tried twrp and cwm.
Is it because when i got the phone it was already on 4.4.4?

cnoevl21 said:
I just bought the developer edition for verizon. I unlocked the bootloader successfully, i installed twrp is cmd and it said it installed successfully. I did not, however, open twrp immediately, which may be the problem. because if i go into download mode and click on recovery, nothing happens, my phone just goes black, like it powers off.
I tried opening cmd window again and installing again, only now the cmd window says the device is not connected, even though it is, or says it can't load the file. and ive tried twrp and cwm.
Is it because when i got the phone it was already on 4.4.4?
Click to expand...
Click to collapse
no that does not matter because you are able to unlock your bootloader so android version dose not matter.
when installing your recovery you are running the CMD commands with your phone in bootloader mode correct.
if you are in bootloader mode and still having issues here are a couple things you can try.
1. Restart the phone
2. try a different USB port
3. restart ADB
4. Check drivers
you already know this but once you flash your recovery make sure you boot into the recovery before booting back into android.
if you get it installed Root is simple just download the SuperSU flashable zip and flash it via your custom recovery.
lmk if you are still having issues and we will look into other issues

thanks!
I ended up deleting everything (adb, sdk, fastboot, etc) and redownloading everything. So that got me able to install twrp, but when i tried to boot into recovery it would turn off the phone. Then I realized that in download mode you scroll down to recovery, then hit vol up to select. I am coming from galaxy nexus where the power button is select. So was i figured this out, i got into twrp and installed superuser, so i am rooted now. Time to find a 4.4.4 rom (may have to wait for a stable one since its pretty new) so i can get rid of all this bloatware. I can freeze some of it in titanium, but a lot of it I'm not sure what it does, again, Ive been on samsung for the past 5 years lol. Thanks again for the help.

4.4.4 isn't new. If you want all the Motorola features, stick with a stock-based rom or stock. I prefer stock with Xposed.

Being on vzw, I would recommend Krypton. It's based off the Verizon image and has a lot of bloatware removed. Xposed will get you about all the customizations you might want past that.

i was looking in the 'Original' development section an saw mostly 442 roms so i assumed 444 was new and didnt have stable roms yet, but now i know where to look and will probably try the krypton rom. gna have to look into xposed and learn what its about since i never used it before.

cnoevl21 said:
i was looking in the 'Original' development section an saw mostly 442 roms so i assumed 444 was new and didnt have stable roms yet, but now i know where to look and will probably try the krypton rom. gna have to look into xposed and learn what its about since i never used it before.
Click to expand...
Click to collapse
Right now Android L or 5.0 Roms are New and buggy. Most 4.4.2 and 4.4.4 roms are stable.
Me personally i like Stock with Xposed and gravity box installed, then i use Titanium Backup there is a battery thread somewhere that list what can and can't be removed. just be careful what you remove or you will end up like me with no active display but everything else about my phone is perfect so i dont want to go back to stock and redo everything.
after xposed and TBU i normally find a launcher i like, then maybe a lock screen but i think i ended up with stock. then i find a Text MSG app i like and other little add-ons to make my phone just for me.
here us a list of what i am running on my Stock Sprint 4.4.4\
LockScreen - Stock but tweaked with GravityBox
Launcher - Google Now Launcher
Text App - Google's Messenger App
Gesture Shortcut Menu - Lazy Swipe( i just found this app about a week ago and so far i love it, it allows me to have a very clean homescreen)
everything else changed on my phone is done threw Xposed and gravity Box.
Here are some App's you might want to check out.
AirDroid
Google Calender(if you use a calendar)
Google Keyboard(my keyboard of choice)
GSam Battery Monitor
Lazy Swipe(listed above)
Lucky Patcher(for thous pesky trial apps)
Pushbullet( alternative app for transferring all kinds of files to and from your device)
Zedge(ringtones and wallpapers)
I also attached some screenshots nothing fancy like i said but i love it and its perfect for me
The first one is my lockscreen, second one is my launcher homescreen, Third one is Lazy Swipe just one of the three tabs.
anyways hope this helps get you started post your setup once you get everything set up to your liking
Good Luck

what is that clock/weather widget? Thats pretty sick

http://forum.xda-developers.com/moto-x/themes-apps/droid-turbo-circle-widget-moto-x-t2941506

nhizzat said:
http://forum.xda-developers.com/moto-x/themes-apps/droid-turbo-circle-widget-moto-x-t2941506
Click to expand...
Click to collapse
yup that is correct enjoy

error while flashing recovry in cmd ....
I have already unlock bootloader successfuly... But when i try to flash custome recovery in fastboot mode with cmd it shows error....
I have tried on different laptops but same ....
Already instlall all drivers ...
Pls help me what to do......!!

commuditi said:
I have already unlock bootloader successfuly... But when i try to flash custome recovery in fastboot mode with cmd it shows error....
I have tried on different laptops but same ....
Already instlall all drivers ...
Pls help me what to do......!!
Click to expand...
Click to collapse
well first thing when u are posting for help you need to include more info. Like for starters what error are you getting so we can figure out what you are doing wrong. post your error and we will go from there.
Thanks

[Q] HTC One 831C - Location India

Dear All,
Two days before , I brought the HTC One (32 GB Golden) which on digging the Phone identity came to know the Model no 831C, later after goggling it came to know that I belongs to Sprint Carrier.
On inserting the code of Hardware components, I found few test/s were not passed and worked normally, other issues are TV app is not recognizing the server, Double Tap Screen wake/sleep works depending on its mood, vDM Client error pops up often.
Request all the experts here to please help me out with the Solution as to how can I make it work flawlessly.
Regards
Karan Adhikari

karan_adhikari said:
Dear All,
Two days before , I brought the HTC One (32 GB Golden) which on digging the Phone identity came to know the Model no 831C, later after goggling it came to know that I belongs to Sprint Carrier.
On inserting the code of Hardware components, I found few test/s were not passed and worked normally, other issues are TV app is not recognizing the server, Double Tap Screen wake/sleep works depending on its mood, vDM Client error pops up often.
Request all the experts here to please help me out with the Solution as to how can I make it work flawlessly.
Regards
Karan Adhikari
Click to expand...
Click to collapse
1) Which tests didn't pass ?
2) Which ROM are you using ?
3) TV app is discontinued by HTC (HTC suggests "Peel Smart Remote")
4) Double Tap Screen Wake works only when you lift up phone and proximity is not blocked (5 seconds cooldown between trying again).
Double tap status bar sleep is buggy on lollipop (this can be different if you have custom kernel)
5) disable vDM client app to prevent popups (you should also disable other sprint apps like HtcSprintService and Self Service SZ)

First of all, thank you for addressing my query & sorry for delay in revert.
Sir, I do know it’s the Sprint phone, as far your concern on below questions, let me try to answer them as below:
1) Which tests didn't pass?
When I run the all functions test by this code (*#*#3424#*#*) in one of the test the error word in green / red appears on screen
2) Which ROM are you using?
I believe it’s the Custom ROM, which would have be provided by Sprint. Software no is 1.54.651.8
3) TV app is discontinued by HTC (HTC suggests "Peel Smart Remote")
No comments, will try to search the PSR on play store.
4) Double Tap Screen Wake works only when you lift up phone and proximity is not blocked (5 seconds cooldown between trying again).
Will strictly follow next time when I do it.
Double tap status bar sleep is buggy on lollipop (this can be different if you have custom kernel)
Its on Android KK 4.4.2
5) disable vDM client app to prevent popups (you should also disable other sprint apps like HtcSprintService and Self Service SZ)
I didn’t find the option to disable vDM app nor did I found other apps of sprint. May I request you to suggest any alternates for it ?
Now, sir my other query is Is it advisable to flash a latest LP rom (i.e Goggle play edition or the rom developed by Bad boys team here) , also it seems that I am S-ON, because when I enter the bootload screen Power + Vol Down key where three android icon at bottom appears , I read LOCKED at the very top of the screen.
Pl. suggest whether it shall be advisable to do it if so request you to suggest the best ROM which shall run flawless in India.
Thanking you in anticipation.
Regards
Karan

Can somebody help me out with this please.. ??
The snapshots of my device are attached hereby, my only query is, and considering the attached images of device can I flash a Custom ROM on to it? Will that be advisable to do so? Are there the chances to Brick the device.
If the answer according to all the Experts here lies in assertive, which ROM is best, since this is a Sprint Device, I have found on the forum that Badboyz rom shall go flawless with any Sprint device, so may I go ahead with it. I am in India presently so wish that all the apps i.e Remote TV, Radio should run properly.
Regards
Karan Adhikari

karan_adhikari said:
The snapshots of my device are attached hereby, my only query is, and considering the attached images of device can I flash a Custom ROM on to it? Will that be advisable to do so? Are there the chances to Brick the device.
Click to expand...
Click to collapse
You need to delete the second and third pictures, there is way to much personal information in there.
The "Locked" at the top of the screen in the bootloader means that the bootloader is locked. If you look directly underneath it you'll see that it says "S-Off". To flash custom recoveries or roms or anything, you need the bootloader unlocked. You can do this using HTCDev, or since you're soff, you can unlock it via adb.
Once you're bootloader is unlocked, you should be set for everything. Flash a custom recovery like Captain Throwback's custom TWRP, get root if you don't have it already, update your firmware, etc. The bad boys xda page has most of this stuff in it.
Note: Your phone is supercid, so you're not limited to just sprint roms.
---------- Post added at 10:31 AM ---------- Previous post was at 10:04 AM ----------
Also, just wondering what exactly were the tests that failed when you did *#*#3424#*#* ?

Thanks a lot sir, I am grateful to you, I have followed you instruction of deleting the images.
Now, last night I did the Factory Hard reset (P+V-DN keys), it went fine, except the data was erased which I never wanted to be backed up though I was haunting of loosing the Sim Lock, but all went fine.
I have my registration on HTCDEV too, and the process of obtaining the TOKENID should go without any hassles.
Now in pursuant to your advise below, will it still be mandatory to unlock the bootloader ? or I may follow the process of wipe/data and then immediately flash the BB's Rom ?
Further, I stand corrected that all the function tests are passed normally, it was my mistake of not placing the Handset on the plain surface while performing one of the test.
Finally, why the model no in phone identity says 831C, and not M8 - May I request your views on this please?
Thanking you once again for addressing, all you guys are rocking, I am here on this forum since 2008, and needless to say "A Proud Member"
All my Best wishes to MEMBERS.
With Regards
K.B. Adhikari
ssantos132 said:
You need to delete the second and third pictures, there is way to much personal information in there.
The "Locked" at the top of the screen in the bootloader means that the bootloader is locked. If you look directly underneath it you'll see that it says "S-Off". To flash custom recoveries or roms or anything, you need the bootloader unlocked. You can do this using HTCDev, or since you're soff, you can unlock it via adb.
Once you're bootloader is unlocked, you should be set for everything. Flash a custom recovery like Captain Throwback's custom TWRP, get root if you don't have it already, update your firmware, etc. The bad boys xda page has most of this stuff in it.
Note: Your phone is supercid, so you're not limited to just sprint roms.
---------- Post added at 10:31 AM ---------- Previous post was at 10:04 AM ----------
Also, just wondering what exactly were the tests that failed when you did *#*#3424#*#* ?
Click to expand...
Click to collapse

karan_adhikari said:
I have my registration on HTCDEV too, and the process of obtaining the TOKENID should go without any hassles.
Now in pursuant to your advise below, will it still be mandatory to unlock the bootloader ? or I may follow the process of wipe/data and then immediately flash the BB's Rom ?
Click to expand...
Click to collapse
Yes, you still need to unlock the bootloader. After that you need to flash a custom recovery.
After doing these two you will be able to flash a custom rom, just make sure you follow all the instructions on the BB rom page

ssantos132 said:
Yes, you still need to unlock the bootloader. After that you need to flash a custom recovery.
After doing these two you will be able to flash a custom rom, just make sure you follow all the instructions on the BB rom page
Click to expand...
Click to collapse
Thanks once again. I am planing to adopt the process of unlocking the bootloader , via HTCDEV and then for flashing the custom Rom, shall seek your guidance hope you won't mind if I bother you for it.
Best Wishes
Karan

Hi ssantos132,
I found there is a SuperSU app preinstalled on my Handset, which prompts me to Grant access when I try to install some other apps from PS- goggle, is my device rooted, because I have found in this link (http://blog.laptopmag.com/root-htc-one-m8), wherein lastly the SuperSU app gets installed automatically.
Pl. guide.
Thanks

Yeah, it looks like you already have root. Try downloading a root checker app from the play store if you want to make sure.

ssantos132 said:
Yeah, it looks like you already have root. Try downloading a root checker app from the play store if you want to make sure.
Click to expand...
Click to collapse
Well thanks for replying. I did that earlier, it says Congratulation your device is rooted. So now when we have concluded that my device is Rooted, the only thing left to be done is, flashing a Custom recovery thru TRWP or CWM right ? Incase if its already been rooted and say if I re-do it, any risk for Device?
Pl. guide.
With Regards
Karan

karan_adhikari said:
Well thanks for replying. I did that earlier, it says Congratulation your device is rooted. So now when we have concluded that my device is Rooted, the only thing left to be done is, flashing a Custom recovery thru TRWP or CWM right ? Incase if its already been rooted and say if I re-do it, any risk for Device?
Click to expand...
Click to collapse
Yeah, once the bootloader is unlocked you can flash a custom recovery then a rom. You can't flash a custom recovery through TWRP or CWM though. Download a custom recovery then use fastboot flash recovery recovery recovery.img

Believe me, That is one rare cellphone you have got.
I am having the same and as I tried few roms, without backing up the radio and replaced it with some random one. Now my phone is just a toy to play with.
I ll suggest you to stick with the rom you are having right now, Take a nandroid backup of the rom, radio and everything else. and keep it safe for future. You will never be able to find them online for this particular phone.
If you would like to help me solve my phone's issue, Please upload the radio. My phone is just laying around in my desk as I have no way to get it to work.

karan_adhikari said:
Dear All,
Two days before , I brought the HTC One (32 GB Golden) which on digging the Phone identity came to know the Model no 831C, later after goggling it came to know that I belongs to Sprint Carrier.
On inserting the code of Hardware components, I found few test/s were not passed and worked normally, other issues are TV app is not recognizing the server, Double Tap Screen wake/sleep works depending on its mood, vDM Client error pops up often.
Request all the experts here to please help me out with the Solution as to how can I make it work flawlessly.
Regards
Karan Adhikari
Click to expand...
Click to collapse
I know about these devices that are being sold in India. I bought a used phone on OLX having same model number with the exact similar problems. I assume these devices are development only devices which don't run a final version of software. I have noticed that most of the issues in the phone are software related. Using my development expertise, I was able to fix most of the problems and upgrade the firmware to Lollipop, however I have messed up the radio and was unable to restore the radio firmware to anything that actually works (This phones come with a radio version that can't be obtained from any online source). If you can provide the radio image from your device, I will prepare a flashable zip to upgrade the firmware to Lollipop which would include the modem you provide, along with instructions on how to unlock the device and flash it to get going. Probably this would iron out the issues that you are facing with your device.
To grab the radio image from your device, use the following command from "adb shell" or Terminal Emulator
Code:
$ su
# dd if=/dev/block/mmcblk0p20 of=/sdcard/radio.img
You will find a file in the sdcard (Internal) named radio.img. Please upload it and provide me with a link.
I would advice you not to make any changes to the device until I provide you with clear instructions on how to do so. Trust me, I really had a hard time with this phone.

Well thanks indeed for the time you took for replying, Sir are you from India Since the name sounds such ?
Secondly, I am desperately looking to upgrade the Software to Latest 5.02 Lollipop from present Kitkat, my basic requirement is that any ROM to which I flash should at least contain the Stock FM Radio, wherein it should be able to tune in the Indian Radio Station.
Confusing issues which keep me scratching my head is that I have pre installed SuperSU app in it. Also I re checked it via installing the app Root Checker which indicated that my device is Rooted. However as and when I tried my device to restart it in Recovery mode it starts normally after a while , the SuperSU app is not getting started.
Can you help me through please. Favor me with (1) Do I need to unlock the Bootloader ? (2) Do I need to flash the custom recovery thru TRWP or CWM ? (3) suggest best Rom which will working with FM Radio (4) A Layman's User Guide to carry out all the process.
Thank You once again.
Regards
Karan Adhikari
dhiru1602 said:
I know about these devices that are being sold in India. I bought a used phone on OLX having same model number with the exact similar problems. I assume these devices are development only devices which don't run a final version of software. I have noticed that most of the issues in the phone are software related. Using my development expertise, I was able to fix most of the problems and upgrade the firmware to Lollipop, however I have messed up the radio and was unable to restore the radio firmware to anything that actually works (This phones come with a radio version that can't be obtained from any online source). If you can provide the radio image from your device, I will prepare a flashable zip to upgrade the firmware to Lollipop which would include the modem you provide, along with instructions on how to unlock the device and flash it to get going. Probably this would iron out the issues that you are facing with your device.
To grab the radio image from your device, use the following command from "adb shell" or Terminal Emulator
Code:
$ su
# dd if=/dev/block/mmcblk0p20 of=/sdcard/radio.img
You will find a file in the sdcard (Internal) named radio.img. Please upload it and provide me with a link.
I would advice you not to make any changes to the device until I provide you with clear instructions on how to do so. Trust me, I really had a hard time with this phone.
Click to expand...
Click to collapse

I will try to help you out definitely, once i am out of my confusion, of taking the Nandriod back up, I will try to upload the img file so your problem is hopefully solved
Thanks
gjmptw said:
Believe me, That is one rare cellphone you have got.
I am having the same and as I tried few roms, without backing up the radio and replaced it with some random one. Now my phone is just a toy to play with.
I ll suggest you to stick with the rom you are having right now, Take a nandroid backup of the rom, radio and everything else. and keep it safe for future. You will never be able to find them online for this particular phone.
If you would like to help me solve my phone's issue, Please upload the radio. My phone is just laying around in my desk as I have no way to get it to work.
Click to expand...
Click to collapse

(1) Do I need to unlock the Bootloader ?
YEs, you must unlock it. It won't affect the phone's basic functunalities
(2) Do I need to flash the custom recovery thru TRWP or CWM ?
Yes. I recommend twrp.
(3) suggest best Rom which will working with FM Radio
None for the phone we are using A Layman's User Guide to carry out all the process.
Please don't upgrade the rom as it might mess with the boot("radio") . Upload your radio and wait for Dhiru's post.

thanks, where shall I get the Radio file please ?
gjmptw said:
(1) Do I need to unlock the Bootloader ?
YEs, you must unlock it. It won't affect the phone's basic functunalities
(2) Do I need to flash the custom recovery thru TRWP or CWM ?
Yes. I recommend twrp.
(3) suggest best Rom which will working with FM Radio
None for the phone we are using A Layman's User Guide to carry out all the process.
Please don't upgrade the rom as it might mess with the boot("radio") . Upload your radio and wait for Dhiru's post.
Click to expand...
Click to collapse

Mr. Dhiru,
Pl intervene and guide me on how do I take the back up and upload the Radio file. So far what I understood is that TWRP toolkit from sites like Rootjunky and follow the youtube video uploaded for it and instal the TWRP and back the radio file and then upload them here for your needful
Pl. guide whether is understanding is correct or not ?
Thanks
karan_adhikari said:
Well thanks indeed for the time you took for replying, Sir are you from India Since the name sounds such ?
Secondly, I am desperately looking to upgrade the Software to Latest 5.02 Lollipop from present Kitkat, my basic requirement is that any ROM to which I flash should at least contain the Stock FM Radio, wherein it should be able to tune in the Indian Radio Station.
Confusing issues which keep me scratching my head is that I have pre installed SuperSU app in it. Also I re checked it via installing the app Root Checker which indicated that my device is Rooted. However as and when I tried my device to restart it in Recovery mode it starts normally after a while , the SuperSU app is not getting started.
Can you help me through please. Favor me with (1) Do I need to unlock the Bootloader ? (2) Do I need to flash the custom recovery thru TRWP or CWM ? (3) suggest best Rom which will working with FM Radio (4) A Layman's User Guide to carry out all the process.
Thank You once again.
Regards
Karan Adhikari
Click to expand...
Click to collapse

Required advice pl. help somebody
Pl. advise as on which TWRP img file should I take into consideration for flashing, since my boot loader is old one the firmware no 4096, Software no is 1.54.651.8, and its sprint 831C (HTC ONE m8). I yesterday tried with the the latest 2.80 twrp img file but got stuck on "Entering Recovery" Screen, some how could manage to come back by Power+Vol up and when the screen got black then Vol Down which took me to boot-loader and then came back by reseting phone. Now the phone is working normal.
I am desperately looking to install CWM or TWRP , so that can take an nandroid backup of the system file, and later post it for the experts here to update the firmware and fix other issues......
snaps of device are attached here
Request all experts to kindly guide me here on it.
Thanking you in anticipation
Karan Adhikari
karan_adhikari said:
Mr. Dhiru,
Pl intervene and guide me on how do I take the back up and upload the Radio file. So far what I understood is that TWRP toolkit from sites like Rootjunky and follow the youtube video uploaded for it and instal the TWRP and back the radio file and then upload them here for your needful
Pl. guide whether is understanding is correct or not ?
Thanks
Click to expand...
Click to collapse

Unable to enter Custom Recovery, Galaxy Pro 10.1 SM-T520 .Help Please, dead Robot

Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !

Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies

Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further

First Root instructions

Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.

AbsoluteContingency said:
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
Click to expand...
Click to collapse
Hi I create a post that might help you, check it out. https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
BTW the moderator will likely move this to the questions area.

AT&T Version ?
New to the RP2 community..
Thinking of getting the AT&T RP2 and wanted to find out/confirm if the AT&T version can be OEM UNLOCKED so you can unlock the bootloader.
Thanks in advance,
RJR
AbsoluteContingency said:
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
Click to expand...
Click to collapse

rrusek said:
New to the RP2 community..
Thinking of getting the AT&T RP2 and wanted to find out/confirm if the AT&T version can be OEM UNLOCKED so you can unlock the bootloader.
Thanks in advance,
RJR
Click to expand...
Click to collapse
I have a rp2, att, bootloader unlocked, rooted, on global pie firmware. Not Sim unlocked, but don't care to move carriers.

jonchance_84 said:
I have a rp2, att, bootloader unlocked, rooted, on global pie firmware. Not Sim unlocked, but don't care to move carriers.
Click to expand...
Click to collapse
Same phone/firmware but I cannot get it rooted. It boot loops or gets stuck at Powered by Android logo with fast boot so at least I can re flash the stock global firmware and boot that. Seems no rooted boot loader works nicely for me. If you have any advice I would appreciate it.

i did fastboot boot_a nd boot_b with reboot but now im stuck on razer loading screen. does this mean im stuck in a bootloop?

It did turn out pretty easy.
I wiped all data, flashed the global MR1 image, booted system and took OTA update to MR2, rebooted to bootloader and flashed Arter 12 kernel, rebooted to Arter TWRP recovery, wiped Dalvik, flashed Magisk 20.1, wiped Dalvik, rebooted system >>> Profit!
Got Edxposed, Gravitybox and Greenify running and all banking apps load perfectly. It's just like the old days of modding, LOL!
Wifi is noticeably improved compared to my previous experience with the phone as well.

Total noob question
gboybama said:
took OTA update to MR2
Click to expand...
Click to collapse
What do you mean? You rooted, then upgraded "normally" to MR2? (I had to look up what OTA is, and it's "over the air"? As in a "normal" upgrade for people who let all their things just update as they please?) I ask because I thought once you rooted, normal updates weren't available?
All the tutorials I find are to upgrade to the MR1 boot.img (which my phone will boot with), then upgrade to the arter97 .img which leaves my phone in an endless booting state. (This is the exact step-by-step I followed: https://forum.xda-developers.com/ra...er-phone-2-t3914996/post79489415#post79489415 -- should be post #94: Castanoff 8th May 2019, 11:07 PM). I started out at MR2, I guess from when I updated the phone to a September update before attempting root. (Its original date was January 2019.)
I'm confused at the whole Magisk thing, as I was assuming that's after the arter update?

Tincan17 said:
What do you mean? You rooted, then upgraded "normally" to MR2? (I had to look up what OTA is, and it's "over the air"? As in a "normal" upgrade for people who let all their things just update as they please?) I ask because I thought once you rooted, normal updates weren't available?
All the tutorials I find are to upgrade to the MR1 boot.img (which my phone will boot with), then upgrade to the arter97 .img which leaves my phone in an endless booting state. (This is the exact step-by-step I followed: https://forum.xda-developers.com/ra...er-phone-2-t3914996/post79489415#post79489415 -- should be post #94: Castanoff 8th May 2019, 11:07 PM). I started out at MR2, I guess from when I updated the phone to a September update before attempting root. (Its original date was January 2019.)
I'm confused at the whole Magisk thing, as I was assuming that's after the arter update?
Click to expand...
Click to collapse
Not at all. I totally factory reset my phone and wiped everything. Flashed the latest stock factory image from Razer that I could find at the time (March 2019?). That put me on the older stock ROM, non-rooted. From there, I just booted into the system and kicked off the (as you put it) "normal" check for updates in the system options. That got me to the September version. Next, I flashed Arter's root and custom recovery kernel IMG file with the bootloader and installed the Magisk zip from TWRP recovery.
Update: Actually, it looks like the build number I'm currently running is now available on the Razer site, so flashing back to an earlier version and taking the OTA update is no longer required. You could just flash their latest system image, which they're putting out there as December 2019. (has the same exact build number as my September build) Then the Arter boot.img and a compatible Magisk zip will complete the root.
Just remember that flashing a full Razer system image in this way will erase your internal (non-SD card) storage. I lost some photos doing this.

Is there any way someone can or has a video on ho wto do this. Or maybe a similar phone thats the same.. But i can just use the specific files for my phone instead... This compared to regualr jailbreaking is like reading chinese. I switched from apple to androd rp2 and i love android way better. But these act more computer based. As far as files and stuff like that

I've been beating my head against the wall here. I've tried both MR0 and MR1. When I type in the fastboot command, all I get is < waiting for any device > My phone is in fastboot mode. I have the right drivers installed. I can see my phone using the adb devices command, so WTF?

scottysize said:
I've been beating my head against the wall here. I've tried both MR0 and MR1. When I type in the fastboot command, all I get is < waiting for any device > My phone is in fastboot mode. I have the right drivers installed. I can see my phone using the adb devices command, so WTF?
Click to expand...
Click to collapse
Try running this tool and see if it helps with fastboot. Let it run it'll boot your phone into the bootloader automatically and install all drivers.
https://forum.xda-developers.com/an...astboot-installer-tool-windows-t3999445/page1