Can anyone help me???
When I turn on my nexus s, it starts CyanogenMod (loop screen).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I turn on to fastboot mode, I cannot use Volume up/down to choose menu.
(view attach file)
What do I do now?
Thanks a lot,
Thai
Just try use nexus root tool kit maybe bootloop Irish usually corrupt flash file or kernel not compatible
Sent from my Nexus S using Tapatalk
makanorang12 said:
Just try use nexus root tool kit maybe bootloop Irish usually corrupt flash file or kernel not compatible
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thanks for your comments.
I try many ways and apps but I cannot.
I think the reasons is my pc cannot connect to the phone. I use "adb devices" command it shows "unauthorized".
In fastboot mode, my pc cannot see the phone.
I try all drivers that I know but it still the same.
I do not know USB debugging mode is enable or not.
tnmthai said:
Thanks for your comments.
I try many ways and apps but I cannot.
I think the reasons is my pc cannot connect to the phone. I use "adb devices" command it shows "unauthorized".
In fastboot mode, my pc cannot see the phone.
I try all drivers that I know but it still the same.
I do not know USB debugging mode is enable or not.
Click to expand...
Click to collapse
Remove all the drivers and just install one driver. I recommend PDANet drivers.
1630
ej8989 said:
Remove all the drivers and just install one driver. I recommend PDANet drivers.
Click to expand...
Click to collapse
yes, I did but it stills the same.
I also try in other pc.
Other ideas please?
tnmthai said:
yes, I did but it stills the same.
I also try in other pc.
Other ideas please?
Click to expand...
Click to collapse
What did you do right before this happens?
Does the volume buttons work before?
digimon04 said:
What did you do right before this happens?
Does the volume buttons work before?
Click to expand...
Click to collapse
First, It can start into ClockworkMod. I used to restore CyanogenMod.
Volume up/down and power work before. They are good when I use ClockworkMod.
Thanks all.
tnmthai said:
First, It can start into ClockworkMod. I used to restore CyanogenMod.
Volume up/down and power work before. They are good when I use ClockworkMod.
Thanks all.
Click to expand...
Click to collapse
a cache wipe/ data wipe might help
but first, you have to find a way into recovery
digimon04 said:
a cache wipe/ data wipe might help
but first, you have to find a way into recovery
Click to expand...
Click to collapse
Thanks. That's my problem.
tnmthai said:
Thanks. That's my problem.
Click to expand...
Click to collapse
Apart from the volume buttons, does the power button work in bootloader mode? I mean even you can't move up/ down, you can still activate "reboot bootloader" in bootloader screen by pushing the power button.
digimon04 said:
Apart from the volume buttons, does the power button work in bootloader mode? I mean even you can't move up/ down, you can still activate "reboot bootloader" in bootloader screen by pushing the power button.
Click to expand...
Click to collapse
Thanks Digimon04,
Yes, I can use power button.
If there is in fastboot, after rebooting it goes back to fastboot.
If I remove battery and press only power button, it goes to CyanogenMod.
I cannot do anything else.
Thanks all,
tnmthai said:
Thanks Digimon04,
Yes, I can use power button.
If there is in fastboot, after rebooting it goes back to fastboot.
If I remove battery and press only power button, it goes to CyanogenMod.
I cannot do anything else.
Thanks all,
Click to expand...
Click to collapse
That means fastboot is working correctly. Did you install Nexus Root Toolkit as suggested in #2?
Inside Nexus Root Toolkit, choose correct phone model and then launch advanced utilities. Navigate to the quick tools and select fastboot-bootloader. Press List devices to ensure that your device is recognized by the PC. Go back and you can flash stock or other ROMs. If your device is not recognized by the PC, you could follow the instruction from the Nexus Root Toolkit to remove and re-install the driver.
Last but not least, I'm afraid you couldn't use adb command in bootloader since the system is not on.
digimon04 said:
That means fastboot is working correctly. Did you install Nexus Root Toolkit as suggested in #2?
Inside Nexus Root Toolkit, choose correct phone model and then launch advanced utilities. Navigate to the quick tools and select fastboot-bootloader. Press List devices to ensure that your device is recognized by the PC. Go back and you can flash stock or other ROMs. If your device is not recognized by the PC, you could follow the instruction from the Nexus Root Toolkit to remove and re-install the driver.
Last but not least, I'm afraid you couldn't use adb command in bootloader since the system is not on.
Click to expand...
Click to collapse
Thanks.
As I mentioned before. In fastboot mode, my pc cannot see the phone. I use "adb devices" command it shows no device.
In CyanogenMod mode (just start screen loop), my pc can see the nexus s but I use "adb devices" command it shows "unauthorized".
I also use Nexus Root Toolkit for device list or somethings you said..
Any idea else ?
Thanks all.
tnmthai said:
Thanks.
As I mentioned before. In fastboot mode, my pc cannot see the phone. I use "adb devices" command it shows no device.
In CyanogenMod mode (just start screen loop), my pc can see the nexus s but I use "adb devices" command it shows "unauthorized".
I also use Nexus Root Toolkit for device list or somethings you said..
Any idea else ?
Thanks all.
Click to expand...
Click to collapse
As your phone can't boot into system, adb won't work. Without the volume buttons, you can't get into custom recovery.
Your phone can only go to bootloader and therefore, fastboot is the only option. If your computer can't see the phone, try replace the USB cable or plug into another USB port. If that still won't work, probably driver on PC might not be loaded correctly. Mere re-installation of driver won't help. I have done it once in the past. You have to pick out all relevant drivers in USBdeview before re-install the driver where Nexus Root Toolkit provide a complete guide.
You may try to press reboot/ reboot bootloader/ reboot recovery under quick tools in advanced utilities of NRT.(remember to select fastboot - bootlaoder). If your phone responds to it, that means driver is loaded and PC can communicate with the phone. You need to make fastboot work before you can do anything to rescue your phone.
digimon04 said:
As your phone can't boot into system, adb won't work. Without the volume buttons, you can't get into custom recovery.
Your phone can only go to bootloader and therefore, fastboot is the only option. If your computer can't see the phone, try replace the USB cable or plug into another USB port. If that still won't work, probably driver on PC might not be loaded correctly. Mere re-installation of driver won't help. I have done it once in the past. You have to pick out all relevant drivers in USBdeview before re-install the driver where Nexus Root Toolkit provide a complete guide.
You may try to press reboot/ reboot bootloader/ reboot recovery under quick tools in advanced utilities of NRT.(remember to select fastboot - bootlaoder). If your phone responds to it, that means driver is loaded and PC can communicate with the phone. You need to make fastboot work before you can do anything to rescue your phone.
Click to expand...
Click to collapse
Many thanks for your guide. I will do it as you said.
But I am busy this week, I will do it next week.
Thanks a lot.
tnmthai said:
Can anyone help me???
When I turn on my nexus s, it starts CyanogenMod (loop screen).
When I turn on to fastboot mode, I cannot use Volume up/down to choose menu.
(view attach file)
What do I do now?
Thanks a lot,
Thai
Click to expand...
Click to collapse
use fastboot and try to return stock (4.1.2) or check your power button, sometimes it's
Related
So official ics update! i was happy! I restored a 2.3.6 backup with cwm and applyed the official zip. But on reboot.. nothing, zero splashscreens, not even google logo. Now if i press power button the screen turn on but it keeps blank and there are no vibrations.. if i release power button then the screen turns off..
Is my nexus s (i9023) in a known state?
Plz help me!
Edit: after some plug/unplug/push/detach ecc i got this nexus s connected to my pc: windows 7 says: "samsung sec s5pc110 test b/d"
i'm googling..
SOLVED!
Big huge thanks to Adam!
Follow his tips here http://forum.xda-developers.com/showpost.php?p=20382688&postcount=16
I had to use a standard linux box, ubuntu virtualizend on vmware fusion didn't work.
With Adam tool you can get both download and recovery mode depending on what hardkey you press (both vol or only vol up) during resurrection.
You are in download mode if search and home softkeys are on
You are in recovery mode if back and menu softkeys are on
You can try the way of recovery mode (with fastboot), for me (i9023) fastboot did not recognize the device.
Download mode solution
After resurrection you'll get a nice download mode (search and home button on and others off, not viceversa).
Now run a virtualized windows (or restart your pc if you have dualboot) and use odin to restore your device (bootloader radio system) to a stock rom like 2.3.3.
Why a virutalized windows or dual boot? Cause if you unplug the device you lose download mode.
Quick how to for odin:
You need samsung drivers installed
Files for european i9023 nexus s: http://www.multiupload.com/A6OP3TFN0I
Googling it seems that they are good also for i9020 amoled nexus s (i'm not responsable about that!)
I used odin v 1.83 (only this version worked for me) on windows. Order of files in odin:
- Bootloader > Bootloader_I9023XXKA3.tar.md5
- PDA > PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5
- PHONE > MODEM_I9023XXKB3_REV_00_CL912571_SIGNED.tar.md5
- CSC > DGS_I9023_EUR.tar
This doesn't solve all problems: at this step i can turn my device on only using a usb powered cable. You need to apply cwm and restore your backup.
So:
Enter recovery mode: plug usb cable (battery appears now!) push vol up and power on.
Apply cwm as usual:
fastboot flash recovery recovery-clockwork.img
Click to expand...
Click to collapse
and enter recovery mode using device interface.
Restore your backup and reboot. Wait for a long boot (need caching all your apps) and it's done!
cyberalex88 said:
So official ics update! i was happy! I restored a 2.3.6 backup with cwm and applyed the official zip. But on reboot.. nothing, zero splashscreens, not even google logo. Now if i press power button the screen turn on but it keeps blank and there are no vibrations.. if i release power button then the screen turns off..
Is my nexus s (i9023) in a known state?
Plz help me!
Click to expand...
Click to collapse
Can you boot into bootloader mode (hold down power + vol-up)?
jvanlew said:
Can you boot into bootloader mode (hold down power + vol-up)?
Click to expand...
Click to collapse
No i can't, screen turns on and off at the pressure of the power button but no way to enter bootloader or recovery mode..
Hey, same thing with me.
When I plug it into the computer, it comes up as SEC S5PC110 Test B/D.
fastboot can't see it, so i can't fastboot it into bootloader. Any help?
narcosis219 said:
Hey, same thing with me.
When I plug it into the computer, it comes up as SEC S5PC110 Test B/D.
fastboot can't see it, so i can't fastboot it into bootloader. Any help?
Click to expand...
Click to collapse
you also got this after ics official update?
try to pull the battery and power up again
cyberalex88 said:
you also got this after ics official update?
Click to expand...
Click to collapse
I downloaded it manually and upgraded.
Battery pull does nothing.
maybe this http://forum.xda-developers.com/showthread.php?t=1257434 could help us! i sent a pm to Adam, we'll see..
I got nexus firmware running on a captivate.. might just work on a nexus too
http://forum.xda-developers.com/showthread.php?t=1247962
I would like a nexus to work with. If someone wants to send me a device, I can locate UnBrickable mod and update my resurrector
The upgrade is only for T-Mobile Nexus S (I-9020T), nither I-9020A nor I-9023!
can you upgrade if you're running 2.3.6 I9020XXKF1
it is a tmo version
Same here. Installed from 2.3.6 and now it won't turn on.
Someone send me a device. Send me a pm. I have a recovery option and I can make your device UnBrickable.
AdamOutler said:
Someone send me a device. Send me a pm. I have a recovery option and I can make your device UnBrickable.
Click to expand...
Click to collapse
Yeap, bricked ones should do nicely.
He's a beast over at the Captivate forum guys.
AdamOutler said:
Someone send me a device. Send me a pm. I have a recovery option and I can make your device UnBrickable.
Click to expand...
Click to collapse
is it possible to post the recovery file here ?
Ibn Saeed said:
is it possible to post the recovery file here ?
Click to expand...
Click to collapse
I already did.. I sent the link.
However, I just finished rewriting the UnBrickable Resurrector for this device.
YOU MUST BE RUNNING A DEBIAN BASED LINUX.
Instructions:
Verify you are running the latest version of Java http://java.com/en/download/installed.jsp
Download UnBrickable Resurrector Revision 37
Right click the app and run with Java
Select "S5PC110 (Nexus S)" From the drop-down list in the app.
Plug in your device
Click resurrect.
Use fastboot to reload software
Let me know if it works
This worked on my Captivate which was in the same mode.
https://plus.google.com/u/0/104711040110222472212/posts/1WhTCszaL3M
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I forgot to mention that you must hold the fastboot key combo
AdamOutler said:
I forgot to mention that you must hold the fastboot key combo
Click to expand...
Click to collapse
So can you provide which DEBIAN Version you use? I encountered the same issue with others.
I think I can install the linux on my laptop and have a try.
yqowen said:
So can you provide which DEBIAN Version you use? I encountered the same issue with others.
I think I can install the linux on my laptop and have a try.
Click to expand...
Click to collapse
I did!
Holy crap people. I don't post this **** for my health. Read my post above and stop sending me PMs.
Managed to get my Nexus S bricked a few hours ago with the ICS update, been spending hours trying to get it working again.
The resurrector has managed to get my device up and running to the Google logo and the padlock screen, now I just need to fix the rest!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I recently unlocked my bootloader and flashed twrp. however when I try to boot into recovery it just keeps booting up as normal. Ive tried PWR & vol+ PWR & vol- and even PWR & Vol +- with no luck at all, I've even tried to re-flashed the recovery image. Cmd says it completes the command. I have no idea why it wont boot into recovery. Please help
xXsim00Xx said:
I recently unlocked my bootloader and flashed twrp. however when I try to boot into recovery it just keeps booting up as normal. Ive tried PWR & vol+ PWR & vol- and even PWR & Vol +- with no luck at all, I've even tried to re-flashed the recovery image. Cmd says it completes the command. I have no idea why it wont boot into recovery. Please help
Click to expand...
Click to collapse
Make sure you have the latest twrp. Download from here: https://eu.dl.twrp.me/maple/ the twrp-3.2.3-0-maple.img. Copy/move the image to your platform-tools. To flash the recovery use: fastboot flash recovery twrp-3.2.3-0-maple.img afterwards close fastboot and unplug your device then press and hold pwr and Vol- until the device vibrates (if you press and hold 'til twrp appears doesn't matter) and it should work.
Hi,
I have a similar problem, searching for solutions now since days and have read tons of tutorials, but nothing helped so far.
Have unlocked my XP Premium, have put it into developer mode and activated USB debugging.
Have installed latest drivers and get a reply (<unlock code> device) when I type "adb devices" in the command window of the platform-tools directory. With "adb reboot bootloader" the phone goes into fastboot mode (blue led is on).
Downloaded the related / appropriate twrp image on my pc (into platform-tools directory) and typed "fastboot flash recovery twrp.img". Got the message <waiting for any device> and nothing else happens.
SuperSU App on my phone says "Root undetected".
Hope you have an advice......
AMHI said:
Hi,
I have a similar problem, searching for solutions now since days and have read tons of tutorials, but nothing helped so far.
Have unlocked my XP Premium, have put it into developer mode and activated USB debugging.
Have installed latest drivers and get a reply (<unlock code> device) when I type "adb devices" in the command window of the platform-tools directory. With "adb reboot bootloader" the phone goes into fastboot mode (blue led is on).
Downloaded the related / appropriate twrp image on my pc (into platform-tools directory) and typed "fastboot flash recovery twrp.img". Got the message <waiting for any device> and nothing else happens.
SuperSU App on my phone says "Root undetected".
Hope you have an advice......
Click to expand...
Click to collapse
Well yours sounds like somc fastest driver is not being picked up. Recommend looking into ur fastboot drivers
lonewolfbtown said:
Well yours sounds like somc fastest driver is not being picked up. Recommend looking into ur fastboot drivers
Click to expand...
Click to collapse
I have tried several times to install and deinstall various drivers that seemed appropriate.
Tried it just again with the drivers from this link
gsmusbdrivers.com/download/adb-fastboot-drivers
(I am yet not allowed to write the complete link)
Installation process completed without errors but it doesn´t changed anything.
I am using Windows 10 and in the device manager I see the Sony driver ("Sony sa0116 ADB Interface Driver").
I also have a section with "Android Device" which contains "Android ADB Interface", "Android Bootloader Interface" and "Android Composite ADB Interface".
Should I see Fastboot drivers somewhere?
Remark: I also tried Flashtool.
When I start the software it says
"Device connected with USB debugging on
Connected device : Sony Xperia XZ Premium
Installed version of busybox : N/A
Android version : 9 / kernel version : 4.4.148-perf+ / Platform : 64bits / Build number : 47.2.A.8.24
Root access denied"
Adb interface is obviously for adb. Still sounds like a fastboot issue cause it'll say adb fastboot, fastboot device etc. When I install my drivers I try doing an advanced reboot and selecting disable driver verification so Google can bugger off and not fail my driver installs. If your having a driver issue that's where I would start. Also put phone in fastboot mode and run command fastboot devices and see what it says. If blank something is still wrong
AMHI said:
Hi,
I have a similar problem, searching for solutions now since days and have read tons of tutorials, but nothing helped so far.
Have unlocked my XP Premium, have put it into developer mode and activated USB debugging.
Have installed latest drivers and get a reply (<unlock code> device) when I type "adb devices" in the command window of the platform-tools directory. With "adb reboot bootloader" the phone goes into fastboot mode (blue led is on).
Downloaded the related / appropriate twrp image on my pc (into platform-tools directory) and typed "fastboot flash recovery twrp.img". Got the message <waiting for any device> and nothing else happens.
SuperSU App on my phone says "Root undetected".
Hope you have an advice......
Click to expand...
Click to collapse
Try doing this when you have your phone in fast boot and connected to your computer:
1. Go into devices manager and find the 'Android phone' icon
2. Right click on it and select 'update driver software'
3. Now select 'browse my computer for driver software'
4. Then select 'Let me pick from a list of device drivers on my computer'
5. Then double click on 'Android bootloader interface' and press OK.
I think that should do it I had a similar problem.
jaskaranb.jb said:
Try doing this when you have your phone in fast boot and connected to your computer:
1. Go into devices manager and find the 'Android phone' icon
2. Right click on it and select 'update driver software'
3. Now select 'browse my computer for driver software'
4. Then select 'Let me pick from a list of device drivers on my computer'
5. Then double click on 'Android bootloader interface' and press OK.
I think that should do it I had a similar problem.
Click to expand...
Click to collapse
Today I had the time for analyzing further with my phone.
Thanks lonewolfbtown for your suggestions.
I started with jaskaranb.jb´s tip first because is seems easier to do.
And: SUCCESS!!!!
I finally now got a reply when preforming fastboot commands.
I am really happy because now it seems I am almost done!
Only drawback is that I now get ´Flashing is not allowed in Lock State´ after I carried out the command "fastboot flash recovery twrp.img" (where twrp.img is the appropriate twrp image for this phone).
The phone is definetly bootloader unlocked. I more than doublechecked this during the last weeks in the service menue (*#*#7378423#*#*).
AMHI said:
Today I had the time for analyzing further with my phone.
Thanks lonewolfbtown for your suggestions.
I started with jaskaranb.jb´s tip first because is seems easier to do.
And: SUCCESS!!!!
I finally now got a reply when preforming fastboot commands.
I am really happy because now it seems I am almost done!
Only drawback is that I now get ´Flashing is not allowed in Lock State´ after I carried out the command "fastboot flash recovery twrp.img" (where twrp.img is the appropriate twrp image for this phone).
The phone is definetly bootloader unlocked. I more than doublechecked this during the last weeks in the service menue (*#*#7378423#*#*).
Click to expand...
Click to collapse
I had the same issue unfortunately it does mean ur bootloader is locked. You can check sony's website to see how to unlock it. The *#*#7378423#*#* tells u if you can unlock it or not if it says yes then your phone has the ability to be unlocked. But big WARNING before unlocking bootloader - JUST MAKE SURE TO DO UR RESEARCH ON DIFFERENT FORMS HOW TO UNLOCK IT. Because I unlocked it through sony's website and I rushed through it, so now my drm keys got deleted (with this some phone features go missing like video enhacment, camera only takes green photos and some more features that I'm not aware of). I fixed my camera by flashing Android 9.0 stock firmware on my phone (idk if other features are back).
jaskaranb.jb said:
I had the same issue unfortunately it does mean ur bootloader is locked. You can check sony's website to see how to unlock it. The *#*#7378423#*#* tells u if you can unlock it or not if it says yes then your phone has the ability to be unlocked. But big WARNING before unlocking bootloader - JUST MAKE SURE TO DO UR RESEARCH ON DIFFERENT FORMS HOW TO UNLOCK IT. Because I unlocked it through sony's website and I rushed through it, so now my drm keys got deleted (with this some phone features go missing like video enhacment, camera only takes green photos and some more features that I'm not aware of). I fixed my camera by flashing Android 9.0 stock firmware on my phone (idk if other features are back).
Click to expand...
Click to collapse
Thanks for your answer.
I am absolutly sure that my phone ist unlocked because exactly this keeps it saying everytime I re-checked it through the service menue (as I wrote in my last sentence). In fact this part I did over and over again.
Regarding the photo and video issue you mentioned I noticed a lot of helpful links during my comprehensive search through all kind of forums regarding my locked issue.
AMHI said:
Thanks for your answer.
I am absolutly sure that my phone ist unlocked because exactly this keeps it saying everytime I re-checked it through the service menue (as I wrote in my last sentence). In fact this part I did over and over again.
Regarding the photo and video issue you mentioned I noticed a lot of helpful links during my comprehensive search through all kind of forums regarding my locked issue.
Click to expand...
Click to collapse
Does your phone show a dialogue when you restart it saying ur phone bootloader is unlocked?
jaskaranb.jb said:
Does your phone show a dialogue when you restart it saying ur phone bootloader is unlocked?
Click to expand...
Click to collapse
No, it starts with the sequence I know from beginning.
First the white screen with "Sony", than whithe screen with "powered by android", then white screen with Xperia logo.
Finally got it!!!
The solution was: due to my fastboot driver problems at the beginning of the whole unlock thing I haven´t really inserted the unlock code.
So now I did and everything is fine: now I do have this warning message about booloader unlock when I start the phone.
Thanks for your support!!!
Hi guys,
i have the same problem. I have unlocked my bootloader (flash screen prompted at the beginning) i flashed maple img (G8141) but i cannot access TWRP neither on PC nor on smartphone. It stacks at sony logo and i have to restart manually.
Tried to update drivers but no success.
Any ideas on how to solve it?
Nereoz said:
Hi guys,
i have the same problem. I have unlocked my bootloader (flash screen prompted at the beginning) i flashed maple img (G8141) but i cannot access TWRP neither on PC nor on smartphone. It stacks at sony logo and i have to restart manually.
Tried to update drivers but no success.
Any ideas on how to solve it?
Click to expand...
Click to collapse
To access TWRP on the phone after flashing, I press Power and Volume- button as long as I see the TWRP screen.
This could take some seconds (10 - 20), depends on the state the phone is in at that time.
AMHI said:
To access TWRP on the phone after flashing, I press Power and Volume- button as long as I see the TWRP screen.
This could take some seconds (10 - 20), depends on the state the phone is in at that time.
Click to expand...
Click to collapse
thank you for your reply. I have tried that combination (plugged and unplugged to PC) but no success.
I have done the same procedure to a Z5 Premium few weeks ago, everything working.
Nereoz said:
thank you for your reply. I have tried that combination (plugged and unplugged to PC) but no success.
I have done the same procedure to a Z5 Premium few weeks ago, everything working.
Click to expand...
Click to collapse
If the TWRP is successful flashed on your phone than it shut worked - unplugged - at described.
At least this works for me (it really takes some time).
Otherwise you might need to use adb / fastboot commands to access the phone again.
AMHI said:
To access TWRP on the phone after flashing, I press Power and Volume- button as long as I see the TWRP screen.
This could take some seconds (10 - 20), depends on the state the phone is in at that time.
Click to expand...
Click to collapse
AMHI said:
If the TWRP is successful flashed on your phone than it shut worked - unplugged - at described.
At least this works for me (it really takes some time).
Otherwise you might need to use adb / fastboot commands to access the phone again.
Click to expand...
Click to collapse
I finally made entering twrp, doing nothing special, maybe I just needed a fresh reboot.
Actually I am experiencing problems with rooting, SuperUser did not work so i gave a try with magisk but to get it work I had to flask a stocke kernel that resulted in a wrong build. Now i have to flash a new ROM and start all over ..
Nereoz said:
I finally made entering twrp, doing nothing special, maybe I just needed a fresh reboot.
Actually I am experiencing problems with rooting, SuperUser did not work so i gave a try with magisk but to get it work I had to flask a stocke kernel that resulted in a wrong build. Now i have to flash a new ROM and start all over ..
Click to expand...
Click to collapse
No you dont, flash a kernel that matches your fw and flash magisk again
Beetle84 said:
No you dont, flash a kernel that matches your fw and flash magisk again
Click to expand...
Click to collapse
Flashed with newflasher and installed magisk. Everything ok now
So I have tried installing twrp on my G8141. After fastboot boot recovery.img, phone rebooted and hangs at SONY logo. My problem now is that no key combination whatsoever seems to do anything now. What can I do? Wait for the battery to drain and then restart?
I mistakenly downloaded and attempted to flash the latest factory image for a Pixel 4 (5G) to my Pixel 4a.
My phone is now stuck on a black screen and I'm unable to boot into the bootloader so that I can flash the correct factory image.
I've tried all sorts of combinations of holding power + volume keys, but nothing seems to work.
The device does some to be on in some fashion as when I plug it into my computer windows alerts me that it's setting up a USB device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Running adb devices and fastboot devices yields no results.
As such the flash-all script included with the factory image doesn't do anything.
I also tried using the "Android Flash Tool" https://flash.android.com/welcome provided by Google, but this also doesn't detect my device.
Are there any other steps I can take to unbrick my phone or is an RMA the only option.
Thanks
I think you're SOL. I did the same thing with my phone and had to send it back to google for a refurb.
AugusDogus said:
I mistakenly downloaded and attempted to flash the latest factory image for a Pixel 4 (5G) to my Pixel 4a.
My phone is now stuck on a black screen and I'm unable to boot into the bootloader so that I can flash the correct factory image.
I've tried all sorts of combinations of holding power + volume keys, but nothing seems to work.
The device does some to be on in some fashion as when I plug it into my computer windows alerts me that it's setting up a USB device.
View attachment 5150333
Running adb devices and fastboot devices yields no results.
As such the flash-all script included with the factory image doesn't do anything.
I also tried using the "Android Flash Tool" https://flash.android.com/welcome provided by Google, but this also doesn't detect my device.
Are there any other steps I can take to unbrick my phone or is an RMA the only option.
Thanks
Click to expand...
Click to collapse
Haha I did the same, don't worry .
I got out of this mess using Android flash tool,
When u plug in the phone hold the volume down button down .....
It might take a while, but it WILL detect the device.
When u pick the rom to flash , in the option to edit make sure to click on wipe , and force partitions.
Good luck
adb and fastboot drivers you must install . Unpack adb and fastboot files to installer , and after unpack tools you can run flashing . Other way don't exist.
AugusDogus said:
I mistakenly downloaded and attempted to flash the latest factory image for a Pixel 4 (5G) to my Pixel 4a.
My phone is now stuck on a black screen and I'm unable to boot into the bootloader so that I can flash the correct factory image.
I've tried all sorts of combinations of holding power + volume keys, but nothing seems to work.
The device does some to be on in some fashion as when I plug it into my computer windows alerts me that it's setting up a USB device.
View attachment 5150333
Running adb devices and fastboot devices yields no results.
As such the flash-all script included with the factory image doesn't do anything.
I also tried using the "Android Flash Tool" https://flash.android.com/welcome provided by Google, but this also doesn't detect my device.
Are there any other steps I can take to unbrick my phone or is an RMA the only option.
Thanks
Click to expand...
Click to collapse
Did you manage to fix this?
I flashing a 4a image to my 4a device and still got the black screen
greeneyez15o said:
Haha I did the same, don't worry .
I got out of this mess using Android flash tool,
When u plug in the phone hold the volume down button down .....
It might take a while, but it WILL detect the device.
When u pick the rom to flash , in the option to edit make sure to click on wipe , and force partitions.
Good luck
Click to expand...
Click to collapse
Are you supposed to have the phone on or off when you plug in the phone with Vol down button down?
But my phone has black screen... how do I tell if the phone is on or off.
Hold power button & volume down at the same time for fastboot screen.
crackerjack1957 said:
Hold power button & volume down at the same time for fastboot screen.
Click to expand...
Click to collapse
Tried that for over 60 seconds. doesn't work.
Problem is like OP the wrong factory image is flashed on the pixel 4a.
The screen just stays blank
greeneyez15o said:
Haha I did the same, don't worry .
I got out of this mess using Android flash tool,
When u plug in the phone hold the volume down button down .....
It might take a while, but it WILL detect the device.
When u pick the rom to flash , in the option to edit make sure to click on wipe , and force partitions.
Good luck
Click to expand...
Click to collapse
Hello,
Not working, the phone in QDL mode, and google flash web tool never detect the phone.
Is there anything to do, or I just through the phone away?
I have goohle 4a flash image 4a 5g.
Phone Going to EDL mode.
I Need mbn loder
How To Unlock Bootloader Galaxy A12.
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
- Go to Settings -> About phone and find your build number.
- Tap on your build number 6 times until you see “You’re now a developer”.
- Go in Developer options > enable OEM unlocking.
- Shut Down your Phone
- Hold Vol + & Vol - and Connect the USB-C Cable
- Device will boot in DOWNLOAD MODE.
- Long press volume UP to unlock the bootloader.
( This will wipe your data and automatically reboot your device! )
- After Reboot the Bootloader is unlocked.
I have done exactly this and the Samsung A12 is now in a boot loop. I have already tried the following:
- Press the power button for a long time.
- Press vol-down+power and if it is turned off only power (https://www.naldotech.com/how-to-fix-bricked-samsung-galaxy-a12-stuck-in-bootloop/)
- Vol-down + vol-up and connect C-USB
- Some variations on this.
UPDATE:
When I tried Vol-down + vol-up and connect C-USB again, it worked and I unlocked the bootloader.
jkaltes said:
I have done exactly this and the Samsung A12 is now in a boot loop. I have already tried the following:
- Press the power button for a long time.
- Press vol-down+power and if it boots only power
- Vol-down + vol-up and connect C-USB
- Some variations on this.
Click to expand...
Click to collapse
Vol-down + vol-up and connect C-USB. You can boot to download mode by this way
It’s how easy Samsung devices are OEM unlocked
1. Tap Build number 7 to 10 times ... You’re now a developer
2. Take software updates
3. Developer settings
4. Allowance of OEM unlocking
5. Start Heimdall (Odin) on desktop to tether your A12 thru USB-C
6. <Vol+> + <Vol-> to reboot to Download mode
7. Long press <Vol+> to unlock bootloader
<Vol+> + <Vol-> + connect C-USB to reboot to Download mode
Hi, I'm new to all this and hopefully I'm just missing something obvious. When I put my A12 into Download Mode, I have no option for a volume-up long-press, as seen in attached photo. I have an A125U model if that information is at all relevant. Developer mode is on, and OEM unlocking is enabled. Not sure where to go from here, any insight would be greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Will this method work on an A12 from ATT that's SIM-locked?
..
crungtrusse said:
Hi, I'm new to all this and hopefully I'm just missing something obvious. When I put my A12 into Download Mode, I have no option for a volume-up long-press, as seen in attached photo. I have an A125U model if that information is at all relevant. Developer mode is on, and OEM unlocking is enabled. Not sure where to go from here, any insight would be greatly appreciated!View attachment 5320891
Click to expand...
Click to collapse
I have the exact same problem.
OEM unlock is toggled ON in developer options.
I cannot get VolUP_VolDOWN + USB to computer to produce download mode so I can unlock my bootloader. All I get is the charging battery %.
Is there any solution to this?
bouyakasha said:
I have the exact same problem.
OEM unlock is toggled ON in developer options.
I cannot get VolUP_VolDOWN + USB to computer to produce download mode so I can unlock my bootloader. All I get is the charging battery %.
Is there any solution to this
Click to expand...
Click to collapse
Same issue tmoble is trying to tell me it automatically unlocked my boot when I Sim unlocked which I'm sure is not true it didn't wipe my data for one
Has anyone tried to use fastboot and use the commands?
Also afterwards, has anyone been able to fastboot boot <kernel_initd.img> to bootstrap over USB from PC?
rob420p said:
Has anyone tried to use fastboot and use the commands?
Click to expand...
Click to collapse
xdabookam said:
Also afterwards, has anyone been able to fastboot boot <kernel_initd.img> to bootstrap over USB from PC?
Click to expand...
Click to collapse
Exactly what I ment
rob420p said:
Has anyone tried to use fastboot and use the commands?
Click to expand...
Click to collapse
I did it just got stuck saying "entering fastboot mode..." In red at top of screen
I also had the same problem as crungtrusse but when i did vol up i got a download screen that i let sit for 15 min and nothing happened
crungtrusse said:
Hi, I'm new to all this and hopefully I'm just missing something obvious. When I put my A12 into Download Mode, I have no option for a volume-up long-press, as seen in attached photo. I have an A125U model if that information is at all relevant. Developer mode is on, and OEM unlocking is enabled. Not sure where to go from here, any insight would be greatly appreciated!View attachment 5320891
Click to expand...
Click to collapse
Goldensnipes said:
I did it just got stuck saying "entering fastboot mode..." In red at top of screen
I also had the same problem as crungtrusse but when i did vol up i got a download screen that i let sit for 15 min and nothing happened
Click to expand...
Click to collapse
You always get "entering fastboot mode..." when you see that screen you are in fastboot.
LAST_krypton said:
You always get "entering fastboot mode..." when you see that screen you are in fastboot.
Click to expand...
Click to collapse
I get no response from phone at that point it dosnt even say its connected to pc
Goldensnipes said:
I get no response from phone at that point it dosnt even say its connected to pc
Click to expand...
Click to collapse
Does that happend when in fastboot? If yes install the adb interface drivers and bootloader iterface drivers.
Looking for deblooted custom rom hmu gala12
TexasAtom said:
Looking for deblooted custom rom hmu gala12
Click to expand...
Click to collapse
Nims? Maybe or do you have the files I can work with that will work too
I am also looking for mcdvoice the same. Have you got any?
How to install Stock ROM - Xiaoxin Pad Pro 2021 [TB-J716F]
I tried installing a GSI-ROM on this tablet, which basically worked except for three/four bugs I coulnd't solve.
So I tried to restore the Stock ROM in the meantime and will share my experience.
Your data will be deleted, try it at your own risk.
Requirements:
Download Stock-ROM and unpack it
Download and install QFIL-Tool + Driver
PC with ADB-Tool
Installation:
Boot tablet in EDL-Mode, there are two ways (in EDL-Mode screen always remains off):
If tablet is fully booted: use adb command "adb reboot edl"
If tablet is off or can't be booted: press the volume up button and hold, plug the usb cable into the tablet and PC and wait a few seconds
Now this should appear in your device manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Start the QFIL-Programm, it should detect the port with the same name.
Go to "Configuration" -> "FireHose Configuration". At device type select "ufs" and tick "Reset After Download" then press ok:
Back in the main window select "Programmer Path" and browse to the ROM-Folder, select the file "prog_firehose_ddr.elf".
Select "Content XML" and browse to the ROM-Folder, select the file "contents.xml"
Click "Download Content" and wait, may take a few minutes
After its done, this status message should a appear and the tablet should reboot.
Done, Stock-ROM should boot now.
Thanks. And relock bootloader and Widevine L1?
Widevine is L3, probably because the bootloader is unlocked.
I haven't tried relocking the bootloader but according to the chinese ZUI website it's not possible to relock.
But you can try it and share you experience, try it with "fastboot oem lock" or "fastboot flashing lock".
HI, How could i use adb since my tab doesnt boot up? It is stucked at bootloop since I receive it from the store
Is your bootloader locked or unlocked? Did you already try to Wipe data/factory reset?
You could try this: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/
Tropaion said:
Is your bootloader locked or unlocked? Did you already try to Wipe data/factory reset?
You could try this: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/
Click to expand...
Click to collapse
It is unlocked but it doesnt even star at all.. only bootloop, i can't put it on bootloader mode or fastboot.. nothing
I can only think of one thing you can try to enter edl mode, which I recently read in an chinese forum.
1. turn off tablet
2 open qfil software
3. hold volume up button
4. plug in usb cable and connect tablet with your pc while holding the button pressed
5. let lose of volume up button
6. wait for about 2 sec., tablet should be in edl mode. qfil software should detect the tablet.
Tropaion said:
I can only think of one thing you can try to enter edl mode, which I recently read in an chinese forum.
1. turn off tablet
2 open qfil software
3. hold volume up button
4. plug in usb cable and connect tablet with your pc while holding the button pressed
5. let lose of volume up button
6. wait for about 2 sec., tablet should be in edl mode. qfil software should detect the tablet.
Click to expand...
Click to collapse
Didnt worked for me either I'll keep trying before return it to the seller..
did you try to relock bootloader then flash stock rom again ? will this method can bring back L1 DRM ?
luizkun said:
did you try to relock bootloader then flash stock rom again ? will this method can bring back L1 DRM ?
Click to expand...
Click to collapse
Didn't tried because my pc even recognize the tablet..
Somehow i managed to get QFIL to recognize the tablet but I'm getting this error..
ThiagoArecippo said:
Somehow i managed to get QFIL to recognize the tablet but I'm getting this error..
Click to expand...
Click to collapse
Which?
Tropaion said:
Which?
Click to expand...
Click to collapse
Hahaha was the sahara fail but I couldn't attach the image I couldn't managed to flash the rom and decided to return it to the seller.. I'm deciding if I get the chinese or global rom. I want widevine L1
Hi @Tropaion , I tried your steps but now the tablet it's stuck in boot. It keeps showing the boot animation, than after a while it stops and the screen turn off. Than nothing. I can still access recovery mode but I can't do anything from there, please help me.
@Cris74m What did the qfil status log say?
Tropaion said:
@Cris74m What did the qfil status log say?
Click to expand...
Click to collapse
it showed the same thing that you posted above (https://forum.xda-developers.com/attachments/qfil_2-png.5434149/), with the download succeed and everything.
Now I am only able to get the computer to recognize the device as this:
@Cris74m Does the non-animated or animated lenovo logo show up?
You can try to go to recovery and do an factory reset/wipe data.
Your device is TB-J716F not TB-J706F?
Tropaion said:
@Cris74m Does the non-animated or animated lenovo logo show up?
You can try to go to recovery and do an factory reset/wipe data
Click to expand...
Click to collapse
As the usual boot. It shows the Lenovo logo with the "powered by android" thing, than it shows the animated logo and after a while it gets stuck and than turn off the screen.
Already tried factory reset but nothing changed.
Somehow I was able to get the laptop to recognize the device and doing a new install using the firhose_lite version; now the device booted correctly, unfortunately it has no google services
@Cris74m How did you manage to get it to recognize it? Change driver?
Just download Google Play Store and install it manually.
BTW did buy your tablet with global ROM and wanted to go back to chinese?