Hey guys, I was trying to root my phone, just so I can overclock it a bit so it goes faster ;_;
and now its stuck at the red triangle and not sure what to do ..... this is what the log thing says...
Starting ADB server...
** daemon not running. starting it now on port 5037 *
* daemon started successfully *
Checking MTD configuration...
Phone uses the old block size.
Firmware version "3.70.651.1"
batter is at 100 percent.
The ADB Shell does not have root permissions. Installing exploit...
Rooting...
Looking for Root...
Got Root!
Checking for needed files...
Pushing res\flash_image to /data/local/flash)image...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
pushing res\URFSOFF.zip to /sdcard/URFSOFF.zip...
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
Bootloader shows Firmware version "1.17.651.1"
hbootpreupdate set at "11"
Verified the phone has the older MTD setup with hBoot version "2.10.0001"
Verified NAND is locked.
Setting RUU mode...
*
* Flashing Firmware...
*
* It is very important that you do not interrupt this while flashing.
* Unplugging or turning the phone off while it is flashing can easily brick
* your phone.
Rebooting...
Waiting for the phone...
Phone is finalizing the flash, waiting...
Waiting for the phone...
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
Found the pohone connected as "device"
Giving the phone time to configure itself...
Rebooting into recovery...
Waiting for the phone...
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
Should I turn the phone off and try turning it on? I don't want to risk breaking it, if its still "flashing" its been stuck at the red triangle for about 10-15 minutes now...
It sounds like maybe the recovery didn't flash correctly. Pull the battery, it wont brick it. Then boot to the bootloader, and see if it is s on or s off. If its s off, we will try flashing a recovery. Give me a minute to get on my laptop, and ill post a recovery for ya.
Sent from my PC36100 using XDA App
Edit: I attatched a PC36IMG of Amon Ra recovery V2.3. Make sure it's just named PC36IMG, and put it on the main directory of your sd card. Boot to the bootloader, and after a few seconds it'll scan and ask you to update. Press Vol up to select yes. After that completes, try entering recovery and see if it worked. (this is all presuming that you are S off)
k2buckley said:
It sounds like maybe the recovery didn't flash correctly. Pull the battery, it wont brick it. Then boot to the bootloader, and see if it is s on or s off. If its s off, we will try flashing a recovery. Give me a minute to get on my laptop, and ill post a recovery for ya.
Sent from my PC36100 using XDA App
Edit: I attatched a PC36IMG of Amon Ra recovery V2.3. Make sure it's just named PC36IMG, and put it on the main directory of your sd card. Boot to the bootloader, and after a few seconds it'll scan and ask you to update. Press Vol up to select yes. After that completes, try entering recovery and see if it worked. (this is all presuming that you are S off)
Click to expand...
Click to collapse
I checked the bootloader and it says that S is still on. @[email protected] I'm gonna try putting your file in the SD card, and try autoroot 2.3 again, or should I use 2.2 ?
no use the newest, there were no code updates after 2 (i think) just updates to the files. try again....
edit: ya i realized where the script went wrong. you got eng build flashed fine, but the bootfrompc recovery never was pushed. just run the script again. if you get stuck at the same place again, just pull the usb and plug back in.
So weird now.... whenever I try running Autoroot 2.3 it says it must be syn... but when I syn it says the following:
=================================
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Checking MTD configuration...
Phone uses the old block size.
Firmware version '1.17.651.1'
Battery is at 82 percent.
Got Root!
Checking for needed files...
ERROR Could not access the SD card!
Make sure your phone is set to charge only and your phone is reading the SD card
properly.
Press any key to exit...
====================================
However, if I try running it in Charge Only mode... it says this....
================
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
The phone could not be found or was not ready. ADB and Fastboot report it as
'disconnected' instead of the expected 'device'. Make sure ADB debugging is
turned on, the phone is in the correct mode and that you are using HTC's Evo
drivers that come with HTC Sync.
Press any key to exit...
====================================
SO CONFUSING @[email protected]
so do what it says... mount in charge only, make sure usb debugging is on (it might have turned off on the eng build, just double check) and plug in nice and snug. i'm sure xhausx will have u all fixed up by tomorrow if i dont first.
Now it says it can't read the SD card in charge mode... omg lol, ima reboot the phone. maybe that will work.
soooo much work, all I wanted to do was overclock the CPU a bit, THATS ALL ;_;
so much easier on the huwai ascend xD
Well... I'm new on this forums, but can provide a small donation if some one can help me root my phone so I can overclock it I already have SetCPU purchased.
I'm kinda noob, so be patient >.<, thanks!
use unrevoked lol.
I dont care how my phone gets rooted, I just want to overclock it, would prefer the easiest most noobiest way of doing it, if you dont mind ^^;;
My friend is good at this stuff, but his away on vacation for the next 2 weeks, what terrible timing :\
unrevoked, I think I tried that? Not sure... could you provide a link? Thanks!!
I was about to say...
Btw you can get much better (and I'm talking like 50% increase) without overclocking by flashing the newest cm7 nightly once it is released...
mic.mayorga said:
use unrevoked lol.
Click to expand...
Click to collapse
Sent from my PC36100
I don't know if it helps but maybe you have an intermittent flaky cable? Only other suggestion that I did, but highly doubt it actually helped me, was literally don't move yourself. What I mean is if you accidentally moved the cable or phone, there could be a less than one percent chance that the data hiccuped.
I really doubt this but when I flashed mine, I was on my bed with the laptop and phone on the palmrest. I didn't move myself on the bed for fear I might cause the phone to brick. It sounds crazy I know!
I doubt it too but with previous phones, the data cable they give you isn't the greatest quality. Sometimes some cables, the microusb plug doesn't seat and lock itself in the socket. I am grasping at straws and this probably isn't what is wrong but it is just ideas...
Or maybe it is a sign that you shouldn't overclock it.
dkdude36 said:
I was about to say...
Btw you can get much better (and I'm talking like 50% increase) without overclocking by flashing the newest cm7 nightly once it is released...
Sent from my PC36100
Click to expand...
Click to collapse
Okay... so I shouldn't root the phone then? I mainly just want to increase its performance and maybe get rid of some of these useless apps it comes with.
I forgot to mention, I bought the phone 2 days ago, from Sprint all stock, and they updated the phone there, so its got all the latest updates and such, and I noticed that interferes with roots? So does that mean I can't root right now?
The only rooting experience I got is from Huawei Ascend Cricket... was easy as downloading file, clicking perma root, and it was done... xD, now if only evo was that easy :S
No of course you can root and you need to in order to flash a rom. Try unrevoked it is also one click
mashalyssa said:
Okay... so I shouldn't root the phone then? I mainly just want to increase its performance and maybe get rid of some of these useless apps it comes with.
I forgot to mention, I bought the phone 2 days ago, from Sprint all stock, and they updated the phone there, so its got all the latest updates and such, and I noticed that interferes with roots? So does that mean I can't root right now?
The only rooting experience I got is from Huawei Ascend Cricket... was easy as downloading file, clicking perma root, and it was done... xD, now if only evo was that easy :S
Click to expand...
Click to collapse
Sent from my PC36100
mic.mayorga said:
use unrevoked lol.
Click to expand...
Click to collapse
Agreed...its the only way I tell people to use
The sd card thing is just a bug in this version, it doesn't recognize the card if you are running the old Eclair software. You can get around it by updating back to froyo or by starting it while the phone is in fastboot or the recovery.
Aha so here is xgausx... I was wondering when you would get here man! So ya listen to him its his auto root script...
xHausx said:
The sd card thing is just a bug in this version, it doesn't recognize the card if you are running the old Eclair software. You can get around it by updating back to froyo or by starting it while the phone is in fastboot or the recovery.
Click to expand...
Click to collapse
Sent from my PC36100
xHausx said:
The sd card thing is just a bug in this version, it doesn't recognize the card if you are running the old Eclair software. You can get around it by updating back to froyo or by starting it while the phone is in fastboot or the recovery.
Click to expand...
Click to collapse
Okay thanks!! I will try it in fastboot, hope it works >_<
Some have also mentioned it working better using htc sync from Sprint instead of HTC's website, may be worth a try.
http://shop2.sprint.com/en/software_downloads/pda_smartphone/htc_evo.shtml
xHausx said:
Some have also mentioned it working better using htc sync from Sprint instead of HTC's website, may be worth a try.
http://shop2.sprint.com/en/software_downloads/pda_smartphone/htc_evo.shtml
Click to expand...
Click to collapse
I got this.
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Searching for phone...
Found the phone connected as 'recovery'
Setting up a temporary Recovery...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Pushing amon_ra_1.8-mod to /...
Checking MTD configuration...
Phone uses the old block size.
Making NANDroid backup, this will take several minutes. Please wait...
NANDroid finished, dumping recovery log...
Setting auto-update command to flash Unrevoked Forever...
Rebooting the recovery...
Waiting for the phone...
Phone is flashing Unrevoked Forever, you should see a circular icon with a green
arrow pointing down for a moment and then it will restart a couple of times...
Phone exited Recovery mode.
Waiting for the phone...
Rebooting into the bootloader...
Waiting for the phone...
Verifying bootloader status...
Bootloader shows Firmware Version '1.17.651.1'
Your NAND is still locked! Rooting Failed.
Rebooting...
Please post your autorootlog.txt file to the XDA thread or send it to me
directly at [email protected]
If your phone is not bootable you can restore it by flashing the RUU through
Fastboot. To get there turn your phone on while holding Vol. Down *NOT VOL UP*,
then push Power to select FASTBOOT. You will see "FASTBOOT USB" highlighted
with red when it is ready.
It is very important that your battery does not die while restoring. If needed
your phone will always be able to charge when turned off.
Press any key to exit...
mashalyssa said:
I got this.
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Searching for phone...
Found the phone connected as 'recovery'
Setting up a temporary Recovery...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Pushing amon_ra_1.8-mod to /...
Checking MTD configuration...
Phone uses the old block size.
Making NANDroid backup, this will take several minutes. Please wait...
NANDroid finished, dumping recovery log...
Setting auto-update command to flash Unrevoked Forever...
Rebooting the recovery...
Waiting for the phone...
Phone is flashing Unrevoked Forever, you should see a circular icon with a green
arrow pointing down for a moment and then it will restart a couple of times...
Phone exited Recovery mode.
Waiting for the phone...
Rebooting into the bootloader...
Waiting for the phone...
Verifying bootloader status...
Bootloader shows Firmware Version '1.17.651.1'
Your NAND is still locked! Rooting Failed.
Rebooting...
Please post your autorootlog.txt file to the XDA thread or send it to me
directly at [email protected]
If your phone is not bootable you can restore it by flashing the RUU through
Fastboot. To get there turn your phone on while holding Vol. Down *NOT VOL UP*,
then push Power to select FASTBOOT. You will see "FASTBOOT USB" highlighted
with red when it is ready.
It is very important that your battery does not die while restoring. If needed
your phone will always be able to charge when turned off.
Press any key to exit...
Click to expand...
Click to collapse
thats kind of weird, can you go into the recovery and use the StartRecovery script to bring up AmonRA on your phone? Once it comes up you will be able to mount the sd card as a disk drive by using the USB MS mode, then look for a file called soff.txt on it. That should show what happened to cause unrevoked forever to fail. Can you also double check whether or not it shows s-on or s-off in your bootloader?
1.Go to autoroot.chainfire.eu
2.Now search the correct file for your
device (WORKS FOR ALL VERSIONS OF THE GALAXY S3)
3.Check against you have downloaded the RIGHT file
4.Now extract the file you have downloaded
5.Run odin as Administrator
6.Click on PDA and choose the CF-AUTO-ROOT..tar.md5 file
7.Shut down your device and go into download mode (hold volume DOWN+power button+home button at the same time)
8.Volume Up to continue
9.Now connect your device with your computer and wait untill odin says (ID:COM Section)
10.Make sure only Auto-Reboot is ticked
11.Click start and wait untill your phone has rebooted
Note: Please be sure you really need the root because :
Your warranty will be void.
If your phone will get hard bricked you won't be able to get your money or a new phone back.
And at least I am not responsible if your device will get hard bricked or anything.
Sent from my GT-I9305 using xda app-developers app
This would be of more use in the I9305 forum .
jje
It works
It worked for me, thx!
I have the international version of GS3 LTE i9305, and it worked just fine
Need help with samsung galaxy S6 edge plus "Custom Binary Blocked by FRP Lock"
Hello Everyone
I am in a serious trouble with my Samsung galaxy s6 edge plus
I bought one in the market used one. i bring it home and it was ok .
The next day from settings i give a reset but now the phone start and giving me message """ Custom Binary Blocked by FRP Lock""" at the start and phone goes shutdown.
I put the phone in Recovery mode and connect the USB cable but neither windows ( 7 and 10) recognise the device error " Device Descriptor Request Failed"
I watched some youtube videos suggesting different techniques but still device is not recognized by Windows.
What should i do i need help Please.
I know you may have already tried, but what happens if you follow the guide for flashing a stock Rom in Odin (so follow the pre-requisits for USB drivers and what not) then put it into download mode (Power Home Vol down then vol up)
I had an FRP issue which soft bricked my s6 edge+, Samsung Switch, Lies and even ADB tools wouldn't detect the device but Odin detected the phone on Com Port 3. If after the device driver installation fails, maybe go into Device Manager, right click on the phone and update drivers manually.. extract the Samsung drivers and point to that directory.
Hi!
I received a bricked teenager's phone to fix, but I don't know if this is possible at all. Maybe someone can help me or at least tell me if this is a hopeless case or not:
The device is a Xiaomi Redmi Note7 (lavender), model M1901F7G. It is soft bricked - I can't start Android to check the MIUI version (suppose it was 11.0.4.something or 11.0.7.something) nor are usb-debugging and/or oem-unlock enabled. This Note7 is on stock firmware and has always been, has never been rooted and as far as I know nothing has ever been done that is beyond official/public Xiaomi updates.
The error description is the device received an update over the air. After installation was completed the Android start failed with the error message "The system has been destroyed". It was still possible to start Android after the command "fastboot continue". Nevertheless the device was in a buggy state: time/date were completely wrong and what was worse: no network connection anymore, not with LTE and also not with WiFi.
In this buggy state userdata has been cleaned. This was to do a 'soft' attempt to repair and not to reset to factory defaults directly - probably not a smart idea, but anyway. Afterwards the phone came up with an initial installation wizard (language and region selection) and reports the device is locked with a Mi Account and needs to be activated. I have access to this account's credentials, but activation fails as there is still no network access available (same as before: no LTE, no WiFi). So I don't see any possiblility to let me enter Android to enable usb-debugging and oem-unlock.
I can access the Note7 via fastboot, but not with adb everything seems to be locked:
Code:
>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.021s]
finished. total time: 0.023s
So I doubt it is possible to do a complete wipe and flash an (older) firmware.
All in all it appears quite strange to me the phone got these problems after an OTA update. I couldn't find any information about others having the same symptoms with a MIUI 11.0.x update on a Redmi Note7. So, might this be a (hidden) hardware defect?
The phone has been bought in 07/2019, it should still be in warranty. My backup solution is to return it to the shop, but I estimate RMA to be processed in 2-4 weeks only (a nightmare for a teenager without smartphone) and I'm still not sure if this case is covered by warranty. Means I - and especially the owner of that device - would be happy if there would be a way to fix it!
Any hints and solutions are highly appreciated!
Kind regards,
Andy
You can not install older version firmware without rooting. Only new version and maybe same version
Maybe this guide can help if you can get into recovery mode (vol up + power)
Thanks a lot! Your guide helped and it worked!
I didn't know which version was installed and also not from which region. So I ended up with some trial and error. I assumed it would be a European or Global version though and just tried the newest ones I could get. In the end I was successfull with MIUI 11.0.7.0 Europe Stable OTA ROM <can't post links yet: bigota[dot]d[dot]miui[dot]com/V11.0.7.0.PFGEUXM/miui-blockota-lavender_eea_global-V11.0.4.0.PFGEUXM-V11.0.7.0.PFGEUXM-35b08eb301-9.0.zip >.
Code:
* Miui sideload made by Francesco Tescari, updated 02 Feb 2018 *
* Checking device status *
* Getting recovery info *
* Creating file MD5 hash *
* Querying ota update server, attempt #0 *
Data partition format might not be necessary and will NOT be done automatically after installation.
If the device doesn't reboot or some apps crash after reboot, you need to manually format the device using "format-data" command!
* Starting sideload *
Sending file to the device... (~100%)
Checking file checksum...
Installing file on the device... (~42%)
* Sideload output: Installation_complete. *
* Rebooting... *
Installation SUCCEEDED!
Please check your device status after reboot to make sure everything is right!
If everything is right and you want to show your gratitude you can offer me a beer by making a donation to this project, do you want to make a donation? [Y/n]
So thanks again! You safed me a couple of hours trying to find out a solution and made a teenager super having for having her phone back! :good: