Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.
Related
Dear All
I'm a new android user, I just get a new A50 from Australia and try to root it. It's successful with z4root and I try to install Thai font to system. Unfortuantely I did wrong by deleting font folder in the system, therefore I can't run the system again. When I power on, it still have only garmin asus android logo and can't use it again. Does anyone please let me know how to restore or resolve this problem, or I have to throw it away? Thank you in advance.
Cheers!
Winext
Android 1.6 or the new 2.1 Eclair update?
It's a new Eclair 2.1 update, is there any solution?
Connect it to your computer via USB cable.
Using ADB, try this:
ADB REBOOT RECOVERY.
If it works, a yellow triangle appears with the green android guy.
Hit the HOME button. A menu appears. Use volume up/down to move through the options. Tap power to select it I beleive.
Reset/wipe to factory is one of the options.
If you need it, ADB is found in the Android SDK.
If that doesn't work, try calling in to Garmin for support.
Sent from my Garminfone using XDA App
Dear Spazmogen
Thank you for your suggestion, but I'm really new with ANDROID.
I downloaded ANDROID SDK and try to install but it dodn't work.
I use Win 7 64bit, do I need another software to run this command.
If possible, please let me know some previous post that already teach for beginner.
Thank you in advance.
Cheers!
Winext
ADB is a command line tool. But you will have to get Android SDK installed on the computer 1st.
Read the instructions for installing the SDK here: http://developer.android.com/sdk/index.html
ADB commands: HERE.
Interesting. I got into the recovery screen using the Quick Boot app,used the home button to show the menu. The arrows and volume buttons move, but can't actually do anything. Probably related to missing files that are reported in the data/cache/recovery folder.
https://www.garminasus.com/en_US/support/eclair/006-B1130-00.update
official 2.1 update came out today for USA GARMINFONES. Not the A50 Nuvifones elsewhere in the world...
Is the update different from the leaked one?
Sent from my Garminfone using XDA App
I am waiting for an answer to that question myself. I have no plans to change from the leaked version Garmin posted in mid-November.
Sent from my Garminfone using XDA App
Apparently someone did a bit comparison and said they matched. Plus, I tried and it told me it was the same version. On the plus side, I messed up my recovery partition and recovered it using the backups I made of each partition after I loaded 2.1 (dump_image). I made img backups and tar backups of all the files in 1.6 (I am anal about backing up). Good thing because 2.1 doesn't come with flash_image.
I can get into fastboot and the driver loads and stuff, but I get no devices listed when I do fastboot devices command. Next stop is Ubuntu
I know it works,just need to know how to get to it. Btw,I tried both the Garmin fastboot and adb drivers as well as adding the device hardware id's into the android drivers and neither worked.
I also need to find out if there is a similar enough kernel that I can use to get a fully functional recovery mode. I did find out that you can use adb just fine in the stock one and it loads a serial driver as well.
any possible way I could get that backup you made? I apparently didnt save my backup to the pc. And currrently I messed up permissions on my Garmin trying to get recovery working. I cant run the update or anything.
I've just stumbled across this forum post from google, I too am need of fixing my phone. All that is faulty is that the recovery mode has been overwritten with an incorrect one. Is it possible to extract the recovery image and reflash it from the optus supplied Android 2.1 006-B1130-00.update file?
Or is there a way of just getting say Rom Manager to work some magic for me?
Yes, it is possible... would be easier if someone could just use dump_image on a phone that has a working recovery mode and root access. I can provide the dump app and instructions.
Where can I get the Optus update, and are you positive recovery works on it? Does it also have working fastboot?
And to the other poster, which partition do you need? Btw, Rom manager has a permission fix mode. I can get you a tar file if it is the system partition or your choice of img or tar for the others.
And to everyone, after updating to 2.1, do a master clear because a lot of 1.6 apps are left over... duplicates.
Also, odexing all apps speeds it up a lot, with the caveat that you have to re-run the odex.sh file (found somewhere here and modified by me to be more thorough) after every app update or you will get force closes.
Oh I just reflashed the update again, and I got my recover menu back!
I'm not sure if i need any help anymore, but thanks for your offer of help merwin.
By working, do you mean that you can get to it with a hardware key combination and can actually select items?
first of all ,i 'm sorry for my english .my a50 is dead too.i also delet font folder and i use the adb command 'adb reboot recovery'.but the error is device not found. and my pohone can not boot .it stop at the android guy . how can i setup the device..Q.......Q......help me ..pls
garmin-asus a50
i have this garmin asus a50 was running 2.1 after installing a few apps.
tried to reboot and now is stuck on android screen.
tried hard reset stuck on android screen with wipe userdata on top
please help!
garmin-asus a50 dead
yoyoset
i think i have the same problem please let me know of any progress
thank you
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
I installed GLTools for the 5th time, I have never had any issues with it before.
Suddenly this time I installed the version of GLTools on XDA forums(this forum!), the phone turned off afterwards, had to manually turn it back on, now it just sits at the Alcatel Boot logo!
I can access the phone with ADB when its turned off and do adb shell, su, with success. Now how can I remove GLTools and restore the phone to normal useage!?
Please somebody help me here, If i get it working again I will never use any software thats not straight from Google Store again!
Please help!
phenom2955 said:
I installed GLTools for the 5th time, I have never had any issues with it before.
Suddenly this time I installed the version of GLTools on XDA forums(this forum!), the phone turned off afterwards, had to manually turn it back on, now it just sits at the Alcatel Boot logo!
I can access the phone with ADB when its turned off and do adb shell, su, with success. Now how can I remove GLTools and restore the phone to normal useage!?
Please somebody help me here, If i get it working again I will never use any software thats not straight from Google Store again!
Please help!
Click to expand...
Click to collapse
get aroma file manager.
go 2 recovery
mount system
flash aroma recovery file mgr
navigate to root/data/app And delete gltools.
go to data/data/(gltools folder) and delete it.
Then go to root partition and delete all 3 texure plugins.
U r done.
possible issue : maybe u messed with the system partition or plugins of latest gltools isn't compatible.
How do i do that if i cant boot the phone?
Please man I am begging you, need to fix this. Cant have another brick on something stupid.
I dont have a custom recovery since there was not one available for my phone. Alcatel OneTouch Fierce XL. Can't I delete the files with adb commands?
You know what happened. I Attempted to try an older version of GLTools 1.97 ealier to see if it would work better to clear up performance of a game, I got rid of that. Then today I went ahead to reinstall 1.99. I suppose the driver files were still installed and are conflicting?
How can I delete them with ADB commands? I have SU access in ADB, just need to know the proper commands and directories to reach and delete the proper files?
phenom2955 said:
How do i do that if i cant boot the phone?
Please man I am begging you, need to fix this. Cant have another brick on something stupid.
I dont have a custom recovery since there was not one available for my phone. Alcatel OneTouch Fierce XL. Can't I delete the files with adb commands?
Click to expand...
Click to collapse
sure.. u can do it with adb too.
but i don't know the process.
Better u ask t3snake in gltools thread.
Hope he will help u
Great now windows applied an update and now my phone is unauthorized! Please tell me I can roll it back and it will be Authorized again?
****ing great now becuase windows updated itself it is unauthorized and I am ****ed.
phenom2955 said:
****ing great now becuase windows updated itself it is unauthorized and I am ****ed.
Click to expand...
Click to collapse
@T3snake
a issue here..
yea think, as if windows had it all plotted against me.... itnt that wierd?
phenom2955 said:
****ing great now becuase windows updated itself it is unauthorized and I am ****ed.
Click to expand...
Click to collapse
If u didnt know It means ur computer isnt authorized anymore(u have to do it after enabling usb debugging for every system)
U can always flash a system.img using fastboot
yea I had authorized it and told it to remember this computer always before the phone bricked. It was working fine last night, I just didnt know what adb commands to use after adb shell and then "SU", from there I should have been able to delete the GLTools drivers if I had known the commands. Then suddenly windows decided in all its glory to update and restart, now its Unauthorized again. So I guess I am ****ed eh? I was hoping a restore point to a couple hours before windows update or rollback the update would set the PC to the same state when It was still authorized, but no Dice huh?
I dont think my phone has a fastboot, the only button combos that work are Power+VolUp, brings up a stock recovery with only 4 options, Restart Phone, Factory Reset, Wipe Cash, and Power down. Thats it.
God this is such bull****, Next droid device I get I am locking down 100% as much as can get and not using anything on it but a few basic apps from GooglePlay.
Thanks anyways though.
So I got a cheap android tablet and I wanted to root it. I was successful so I decided to install TWRP. I searched for my specific model and found an image on a german forum. I downloaded and flashed it and it got stuck in a reboot loop. So I looked at the image and it was for the QV1030. I tried to get it into recovery but couldn't. Many sources told me to hold Vol Up and Lock, and I tried this and more. Nothing would make it enter recovery mode. Then I read about SP Flash Tool and found the stock rom for the tablet and decided I would try to flash that. It kept coming up with an error, and every source online told me to format the flash except for the bootloader and then I could flash it. So I did. Now it doesn't show anything on screen, and SP Flash Tool comes up with error 6045. But it does show up in device manager under com ports as, "MediaTek USB Port" so I think I can still do something about it. I don't have any backups. I don't know what I'm doing. I require assistance please.
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
drsinclair said:
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
Click to expand...
Click to collapse
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
drsinclair said:
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
Click to expand...
Click to collapse
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
drsinclair said:
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
Click to expand...
Click to collapse
I actually want to upgrade this from Android 4.2.2 to a more recent version. Do you guys have any ideas about that?
So I've come to the conclusion that while the device is no longer bricked, the current installation is written over the old one and things are conflicting. I know this because I looked through the cache and found filenames referring to apps I had installed before breaking it. So would the solution be to wipe the system partition and reflash the system.img so everything is fresh? Or does the problem lie elsewhere.
I formated the system partition, used SP Flasher to flash system.img and then did a factory reset. The issue has still not been solved. And now that I have done that, I don't have root access anymore. Framaroot says it was successful and I restart and check root explorer on ES File Explorer and it doesn't work.
I gained root access using a different method. However the WiFi still doesn't work. I think it may be that the mac address information was from the backup I flashed from the internet, and therefore doesn't match. I found a guide that tells me how to hex edit a file and put in my real mac address, but it's unavailable under wifi. I don't have the sticker on the back that says it either. How else can I find it?
Turns out the mac address can be anything. I used SN Write tool and an AB DB for my chipset and it still didn't solve the problem. I have no idea what to do. Can anyone help me?
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
help - link
drsinclair said:
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
Click to expand...
Click to collapse
Hey man! I have the same problems with my QV 830. Can you give me the link for system.img and secro.img, please?
Here was a Guide. Someone said people don't care about Me or My Work so...
This doesnt work on US model of Xperia 5 IV ( XQ-CQ62) because Sony isnt allowing bootloader unlock in USA.
Meaning you cannot get unlock codes for your phone thru sony website ,thats a crucial step in this guide.
hello, i've tried flashing the patched file onto my device but it just seems to bootloop, i'm currently running 64.1.a.0.857
viper. said:
This doesnt work on US model of Xperia 5 IV ( XQ-CQ62) because Sony isnt allowing bootloader unlock in USA.
Meaning you cannot get unlock codes for your phone thru sony website ,thats a crucial step in this guide.
Click to expand...
Click to collapse
Wow......glad I got the JP version of a new phone for once! Otherwise it's still blowing my mind that Sony itself isn't scrutinizing root like damn-near every other manufacturer as of late.
It's been more than 7 years since I rooted my last phone. Now is everything very different. Thanks for the thread, I know what I will do this weekend.
Just got my 5IV (UK) and exactly the guide I was looking for but just a simple question
My last personal Sony was the Z3C and unlocking bootloader/rooting that had drm issues with the official camera etc
Does unlocking bootloader with 5IV have any app issues, do the camera apps all work exactly as before and any other imporant Sony apps?
Will I be able to use Sony OTA updates?
If all good, I'll be unlocking and rooting this weekend, cant wait.
Thanks
rawdealer said:
It's been more than 7 years since I rooted my last phone. Now is everything very different. Thanks for the thread, I know what I will do this weekend.
Click to expand...
Click to collapse
Bruh! You and me both!! I finally rooted my Asus Zenphone 6 this past October. A bunch of reading and forums lol. Also back 7-8 years ago there were plenty of Youtube videos. Now not so much! My Zenphone 6 just died today and I am 90% sure I'll be getting the Xperia 5IV which I was eyeing since announced. I was hoping my Zenphone would have given me one more year, but alas. I'm visiting here to get the scoop on rooting this in the event I want to. I feel your pain!
smudgy636 said:
hello, i've tried flashing the patched file onto my device but it just seems to bootloop, i'm currently running 64.1.a.0.857
Click to expand...
Click to collapse
HI, not sure if you solved it, had the same issue. So, as it gave an option to do full user reset (or something like that) I chose it. It then rebooted and I was back into the phone with the initial setup again.
I then re-installed the latest magisk app and it showed that magisk/root is installed.
As a test, I then installed f-droid and installed Adaway. I chose to configure in root mode,
the 'grant access' dialogue popped up and boom, root access provided.
Btw, if you do want to install Adaway too, enable systemless host in magisk preferences.
Trying it now... It's a bit of a hassle, but that's on Sony.
Edit: yep, works an absolute treat. One little remark: Wiping after installing Magisk isn't neccesary, afaict. Perhaps make it optional "in case of weird problems".
thany2 said:
Trying it now... It's a bit of a hassle, but that's on Sony.
Edit: yep, works an absolute treat. One little remark: Wiping after installing Magisk isn't neccesary, afaict. Perhaps make it optional "in case of weird problems".
Click to expand...
Click to collapse
So, no need to wipe all user data or?
how to hide root from GooglePay?
So I'm getting stuck on the OEM unlock bit. After entering the command I get this:
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.004s
Click to expand...
Click to collapse
Any Ideas?
hasztagL said:
how to hide root from GooglePay?
Click to expand...
Click to collapse
Why would you need to? Play works perfectly fine with non-hidden root.
Either way, try enabling Zygisk in the Magisk manager. You might also have to check to enforce the DenyList, and check the Play app on the DenyList.
But really it's not neccesary in my experience. The only app that refuses to work properly is my banking app. In their infinite stupidity they demote rooted users to a PIN code instead of fingerprint, even though on a rooted device, the fingerprint is still more secure. But I digress, sorry.
Skv012a said:
So, no need to wipe all user data or?
Click to expand...
Click to collapse
I guess it was a catchall. Maybe if you've already been tinkering a lot, it might be a good idea to "start over", since Magisk can completely fluff up you phone if it's being interfered with. However, my phone was completely stock, other than being bootloader-unlocked, so in my case the answer is no, not needed.
No promises though. Just give it a go. Do have a backup ready.
thany2 said:
Why would you need to? Play works perfectly fine with non-hidden root.
Either way, try enabling Zygisk in the Magisk manager. You might also have to check to enforce the DenyList, and check the Play app on the DenyList.
But really it's not neccesary in my experience. The only app that refuses to work properly is my banking app. In their infinite stupidity they demote rooted users to a PIN code instead of fingerprint, even though on a rooted device, the fingerprint is still more secure. But I digress, sorry.
Click to expand...
Click to collapse
Google Wallet not work with root. With DenyList still not work.
Matrixclonk said:
So I'm getting stuck on the OEM unlock bit. After entering the command I get this:
Any Ideas?
Click to expand...
Click to collapse
It looks like you started fastboot mode. You should enter bootloader mode for the fastboot command for some reason
Also I had a problem in bootloader mode and had to manually update the driver in Windows for the phone.
When I was in bootloader, the adb devices and fastboot devices commands did not return anything, meaning the phone wasn't found.
So if someone else's phone isn't recognized in fastboot/bootloader mode you could try installing the driver manually like so:
Open the Device Manager in Windows and under under Other devices (probably), there will be a device named Android with a question mark (meaning no driver or problem with it.)
Then right click on it -> Update driver -> Browse my computer for drivers -> Let me pick from a list of available drivers... (you should have installed the drivers from windows (in file explorer, right click, install on the .inf file))
Then there under Android, from Google I had the ADB Interface driver which I selected and Installed it forcefully.
And after that fastboot comand worked normally.
alexdo said:
It looks like you started fastboot mode. You should enter bootloader mode for the fastboot command for some reason
Also I had a problem in bootloader mode and had to manually update the driver in Windows for the phone.
When I was in bootloader, the adb devices and fastboot devices commands did not return anything, meaning the phone wasn't found.
So if someone else's phone isn't recognized in fastboot/bootloader mode you could try installing the driver manually like so:
Open the Device Manager in Windows and under under Other devices (probably), there will be a device named Android with a question mark (meaning no driver or problem with it.)
Then right click on it -> Update driver -> Browse my computer for drivers -> Let me pick from a list of available drivers... (you should have installed the drivers from windows (in file explorer, right click, install on the .inf file))
Then there under Android, from Google I had the ADB Interface driver which I selected and Installed it forcefully.
And after that fastboot comand worked normally.
Click to expand...
Click to collapse
Thanks man, I was in fastboot because when I went to bootloader I always got the message waiting for device. Also weird I had to reinstall the driver each time i went into bootloader :S
@Miustone Hey. I rooted my phone following your guide and I have a question.
Sony have released an update was wodnering if I flash the latest update, will my settings/data be intact? Apparaently the update is only small, just wish I could flash that...not the whole 3.3GB
Thanks
After getting said from some Stock Tree ROM Cookers that People wont miss Me around Xperias (and that i havent developed that much), i just decided to take My Work offline and to remove also My Guides. Sorry for everyone who apprecciated My Contributions but You will get Stock FW based ROMs instead (one Day)! It wont have the quality or safeness of a good old SODP based ROM (since they refuse to work with it on a disrespectful way) but hope You will be fine with it somehow!
All the Best for the future,
Miu
Miustone said:
After getting said from some Stock Tree ROM Cookers that People wont miss Me around Xperias (and that i havent developed that much), i just decided to take My Work offline and to remove also My Guides. Sorry for everyone who apprecciated My Contributions but You will get Stock FW based ROMs instead (one Day)! It wont have the quality or safeness of a good old SODP based ROM (since they refuse to work with it on a disrespectful way) but hope You will be fine with it somehow!
All the Best for the future,
Miu
Click to expand...
Click to collapse
sad. i love your work.