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!
Hi,
today in the morning I couldn’t turn on my S7. It went off while charging overnight. Then I tried to hold the volume down and the power button together for twelve seconds and the S7 turned on. Unfortunately it just boots to the Samsung logo and nothing happens since then.
I wrote to the Samsung support and they told me to send it in. And they also said that I will lose my warranty if I make a hard reset. Is that true? Because the other thing is, that I really need some very important data from just one app. I already did a hard reset in the past and the data from this app didn’t get lost. I don’t know why (no cloud synchronization) but it worked. My plan was to try a hard reset but my phone is fully charged and I cannot turn it off to get into Recovery mode.
So basically I have three questions:
1. Will I lose my warranty if I do a hard reset?
2. Is there any possibility turn off my phone or to unload my battery? (And after that to try a hard reset.)
3. Does anyone have any idea how to save some date by any other way?
Thank you very much for any help!
Samsung are full of sh** if they told you you would lose warranty by performing a full reset, nothing of the sort
Warranty is checked by KNOX 0x0 = valid (Or 0x1 if it is tripped) which is only tripped by flashing something custom / rooting
Try booting into recovery and clearing only the caches, see if you can get back in that way
Otherwise, flashing the same stock ROM over the top with ODIN may work
Thank you for your answer.
Any idea how to boot into recovery mode? The problem is that in the moment I cannot turn off my phone and it's fully charged. I guess it would last some days to wait until the battery is empty. And unfortunately you can't remove the ****ing battery.
robsen1 said:
Thank you for your answer.
Any idea how to boot into recovery mode? The problem is that in the moment I cannot turn off my phone and it's fully charged. I guess it would last some days to wait until the battery is empty. And unfortunately you can't remove the ****ing battery.
Click to expand...
Click to collapse
Volume up & Home & Power
Keep those buttons held in until the phone reboots, continue holding them and it should reboot a 2nd time, this time hopefully entering recovery
You can try the same for download mode, which is the same combo, only volume down instead of up
*Detection* said:
Volume up & Home & Power
Keep those buttons held in until the phone reboots, continue holding them and it should reboot a 2nd time, this time hopefully entering recovery
You can try the same for download mode, which is the same combo, only volume down instead of up
Click to expand...
Click to collapse
I did this combo. Following message did pop up:
"Warning
A custom OS can cause critical problems in phone and installed applications. If you want to download a custom OS, press the volume up key. Otherwise, press the volume down key to cancel."
First i pressed the volume down button and then nothing happened and it booted again until the Samsung logo. In my second try I pressed the volume up button and now I am here (see attached pics).
{
"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"
}
Any advice?
robsen1 said:
I did this combo. Following message did pop up:
"Warning
A custom OS can cause critical problems in phone and installed applications. If you want to download a custom OS, press the volume up key. Otherwise, press the volume down key to cancel."
First i pressed the volume down button and then nothing happened and it booted again until the Samsung logo. In my second try I pressed the volume up button and now I am here (see attached pics).
[/hide]
Any advice?
Click to expand...
Click to collapse
Well that's download mode where you can flash the stock ROM with ODIN, so you can at least flash stock again, which may work, but I would try recovery first though, the first combo I posted with Volume Up
*Detection* said:
Well that's download mode where you can flash the stock ROM with ODIN, so you can at least flash stock again, which may work, but I would try recovery first though, the first combo I posted with Volume Up
Click to expand...
Click to collapse
I tried the combo with the vol up key and I came to the exact same menu which I described above. (Then I pressed the volume down key and the phone boooted to the Samsung logo).
Now only the combo with the vol down key works. If I press vol up + home + power nothing happens. I don't get this ****.
robsen1 said:
I tried the combo with the vol up key and I came to the exact same menu which I described above. (Then I pressed the volume down key and the phone boooted to the Samsung logo).
Now only the combo with the vol down key works. If I press vol up + home + power nothing happens. I don't get this ****.
Click to expand...
Click to collapse
OK, it's possible that recovery got corrupted then
Right, so grab a stock ROM from here
http://updato.com/firmware-archive-select-model?q=G930F
Extract and Load the .MD5 into ODIN AP section
Put the phone into download mode and hit start
It should reboot hopefully into a working OS
if not, try entering recovery again
ODIN
http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
*Detection* said:
OK, it's possible that recovery got corrupted then
Right, so grab a stock ROM from here
http://updato.com/firmware-archive-select-model?q=G930F
Extract and Load the .MD5 into ODIN AP section
Put the phone into download mode and hit start
It should reboot hopefully into a working OS
if not, try entering recovery again
ODIN
http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Click to expand...
Click to collapse
So do I loose my warranty if I do this?
(Sorry for my dumb quesiotns and thank you for your help...)
robsen1 said:
So do I loose my warranty if I do this?
(Sorry for my dumb quesiotns and thank you for your help...)
Click to expand...
Click to collapse
No, as I said earlier, warranty is only affected if you flash something custom
Stock Samsung ROMs are not custom
For a very short time my phone startet adnroid, but everyhing was black und I just saw the notifications bar. I couldn't do anything. After that my phone did a reboot and now I am again at the Samsung logo. The combi with vol up still doesn't work.
robsen1 said:
For a very short time my phone startet adnroid, but everyhing was black und I just saw the notifications bar. I couldn't do anything. After that my phone did a reboot and now I am again at the Samsung logo. The combi with vol up still doesn't work.
Click to expand...
Click to collapse
You managed to download and flash a stock ROM in that short time?
Might need to flash the entire set of files from the ROM download in ODIN, which I think might reset the phone with one of them (HOME I think)
EDIT - Another option would be firmware recovery using SmartSwitch
http://www.samsung.com/uk/smart-switch/samsung-desktop-app.html
Good day.
Recently happened to me something similar, while i was playing, the phone rebooted and got stuck at samsung logo.
The phone was rooted, with TWRP and Xposed.
Really don't know what happened. At the time, in panic, i flashed a stock ROM and the phone never booted again. Just a blank screen and a blue led.
I sent my phone to Samsung for warranty and 1 month later (5 days ago), got it back working, even with KNOX 1x0.
In most of Europe, Samsung cannot charge you anything even if the phone was rooted, with the exception if it was root that directly caused the malfunction.
I am having the same problem. the combo with Vol up does not work. Any further help, PLEASE?
Hello,
I bought a Samsung Galaxy A20e, model name : SM-A202F/DS
First I unlocked the boot-loader,
then I flashed a TWRP custom recovery that I downloaded here :
https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view
The custom recovery was working well. I tried to flash an another kernel in order to flash another system (various Android GSI I could find).
Apart from one kernel that seams to be flashed correctly from TWRP, no System would boot at any time.
So I decided to go back to the stock ROM of the phone temporarily.
To do so I found one on the internet, went to Download mode, and tried to flash it with Odin (v3.14.1).
The flash was unsuccessful. At that point I came with a blue screen (similar to download mode) telling me that I should use Samsung emergency recovery function in the Smart Switch PC software.
I installed this software (made all updates available) and went to the dedicated section. Unfortunately, no phone could be detected for recovery. But the PC could still detect the phone at that time.
So I decided to flash just the kernel (from stock archive) with Odin if I remember well. (unchecked other parts).
And since that, my phone is bootloop-ing when I plug it to the computer.
The screen first displays classic Samsung logo with model phone name and warning due to unlocked boot-loader.
And 2 seconds later, a little portion of the screen (top left) displays a message starting with:
“KERNEL REV. CHECK FAIL. DEVICE: 3, BI…” I can’t read the rest due to the front camera placement. I found results on the internet that it could be “kernel rev check fail-device:3 binary:x boot” for example. This message and only the text part is “backgrounded” with the same color as the Download mode blue color. And 5 seconds later the phone reboot for the same sequence.
{
"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"
}
Boot Img link [ https://img.vj.romanet.fr/samsung_a20e_sm-a202f-ds_bootlooping_1.jpg ]
I tried all combinations that could possibly bring me to the download mode or any recovery that could still be there.
Vol UP + Vol DOWN
Vol UP + Vol DOWN + PWR
Vol UP + PWR
Vol DOWN + PWR
Vol UP + Cable Plug
Vol DOWN + Calble Plug
Vol UP + Vol DOWN + Cable Plug
etc
The phone is still bootloop-ing if let plugged (USB to PC or USB to Charger), and get never detected by the computer. Neither on Windows 10 (previously detecting the phone) nor on Linux with "ADB devices" or "Fastboot devices" commands. I used 2 different cables including the one given with the phone.
I found a post on this forum, telling it could be due to damaged power button. I opened the phone, unlike the side panel buttons cable from the motherboard, same result.
If you have any ideas, they are welcome
Sorry for this huge post, hope my English is clear enough
Thank you very much and happy new year !
try heimdall, but dont use the gui, go on the internet find the instructions to flash all the nesscerray files, and done, i had a problem where my phone kept bootlooping back to download mode( bassicly i bricked it) and because i had linux i had to use heimdall to flash all files within the stock image
milosOnThePhone said:
Hello,
I bought a Samsung Galaxy A20e, model name : SM-A202F/DS
First I unlocked the boot-loader,
then I flashed a TWRP custom recovery that I downloaded here :
https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view
The custom recovery was working well. I tried to flash an another kernel in order to flash another system (various Android GSI I could find).
Apart from one kernel that seams to be flashed correctly from TWRP, no System would boot at any time.
So I decided to go back to the stock ROM of the phone temporarily.
To do so I found one on the internet, went to Download mode, and tried to flash it with Odin (v3.14.1).
The flash was unsuccessful. At that point I came with a blue screen (similar to download mode) telling me that I should use Samsung emergency recovery function in the Smart Switch PC software.
I installed this software (made all updates available) and went to the dedicated section. Unfortunately, no phone could be detected for recovery. But the PC could still detect the phone at that time.
So I decided to flash just the kernel (from stock archive) with Odin if I remember well. (unchecked other parts).
And since that, my phone is bootloop-ing when I plug it to the computer.
The screen first displays classic Samsung logo with model phone name and warning due to unlocked boot-loader.
And 2 seconds later, a little portion of the screen (top left) displays a message starting with:
“KERNEL REV. CHECK FAIL. DEVICE: 3, BI…” I can’t read the rest due to the front camera placement. I found results on the internet that it could be “kernel rev check fail-device:3 binary:x boot” for example. This message and only the text part is “backgrounded” with the same color as the Download mode blue color. And 5 seconds later the phone reboot for the same sequence.
Boot Img link [ https://img.vj.romanet.fr/samsung_a20e_sm-a202f-ds_bootlooping_1.jpg ]
I tried all combinations that could possibly bring me to the download mode or any recovery that could still be there.
Vol UP + Vol DOWN
Vol UP + Vol DOWN + PWR
Vol UP + PWR
Vol DOWN + PWR
Vol UP + Cable Plug
Vol DOWN + Calble Plug
Vol UP + Vol DOWN + Cable Plug
etc
The phone is still bootloop-ing if let plugged (USB to PC or USB to Charger), and get never detected by the computer. Neither on Windows 10 (previously detecting the phone) nor on Linux with "ADB devices" or "Fastboot devices" commands. I used 2 different cables including the one given with the phone.
I found a post on this forum, telling it could be due to damaged power button. I opened the phone, unlike the side panel buttons cable from the motherboard, same result.
If you have any ideas, they are welcome
Sorry for this huge post, hope my English is clear enough
Thank you very much and happy new year !
Click to expand...
Click to collapse
the same happened to me, idk how I put the phone in download mode once. there should be a way but idk
linkmast3r said:
the same happened to me, idk how I put the phone in download mode once. there should be a way but idk
Click to expand...
Click to collapse
I found an app on windows that was able to put my android into download mode, after it did that I used the program to restart my device and quickly pushed the download mode buttons and flashed a stock rom
I also have this problem but I can't put the phone in download mode and I'm not sure what to do.
Xellerate said:
I found an app on windows that was able to put my android into download mode, after it did that I used the program to restart my device and quickly pushed the download mode buttons and flashed a stock rom
Click to expand...
Click to collapse
name¿?
linkmast3r said:
name¿?
Click to expand...
Click to collapse
ReiBoot for android, when connecting your device it automatically put you in download mode, even though it won't look like it, using the program click exit download mode, it will put you in the boot option, quickly hold the power and the volume to enter the recovery options and choose download mode
Xellerate said:
ReiBoot for android, when connecting your device it automatically put you in download mode, even though it won't look like it, using the program click exit download mode, it will put you in the boot option, quickly hold the power and the volume to enter the recovery options and choose download mode
Click to expand...
Click to collapse
it sais it is for iOS in the official page, it works also for samsung?
linkmast3r said:
it sais it is for iOS in the official page, it works also for samsung?
Click to expand...
Click to collapse
There're obviously an Android and an iOS version available but they are paid applications.
It is paid but you don't need to pay for it, you can still use it without paying, It will still get you into download mode, that's free
Hey guys,
I just brought my phone (samsung SM-a202f) back from the dead it was stuck in emercency mode (asking to connect to smart switch) after I did something wrong flashing TWRP. I did it a million times but appearently I screwed up because my phone was stuck in the emercency mode bootloop and Odin did see the phone in emercency mode, but could not flash stock rom with or without bootloader.
I knew I had the right firmware (thanks to samfirm) and found the PIT file in the SCS .tar.md5 file. Just remove the .md5 of the name of the scs file and then unzip so you have the PIT file. What you do is feed that to odin under the pit tab and then use Odin like you normally would use it to flash a complete Rom on it.
Hope this helps someone. Happy 2022!
I bought a used Samsung Tab S2 SM-T819 with Lineage 17.1 already installed.
I would like to install the original stock firmware. Is this possible? If it is, how exactly do I do this?
I apologize if this question has been asked a trillion times, just trying to get the best method to use in 2021. I'm looking for the method with the least chance of bricking the device.
Thanks
dude_48 said:
I bought a used Samsung Tab S2 SM-T819 with Lineage 17.1 already installed.
I would like to install the original stock firmware. Is this possible? If it is, how exactly do I do this?
I apologize if this question has been asked a trillion times, just trying to get the best method to use in 2021. I'm looking for the method with the least chance of bricking the device.
Thanks
Click to expand...
Click to collapse
Download Samsung Galaxy Tab S2 SM-T819 SEE South East Europe firmware
All Samsung firmwares for Galaxy Tab S2 in South East Europe with model code SM-T819. We offer free and fast download options. Check them out now.
www.sammobile.com
Choose the firmware based on carrier and country.
Check the number closely with about phone.
Boot the tab to download mode by power+vol down
Flash with Odin.
Thanks for the info.
I followed the instructions on the link you posted.
I used ODIN, everything looked good, I got a green "passed" flash.
The tablet looked like it was rebooting, then "installing security updates" was displayed on the tablet screen for about 20 seconds. It looked like it was rebooting, however the "Samsung" logo on screen is going dim/bright and it will not boot.
I tried holding the power button down for 30 seconds and I can't get it to turn off, or restart.
Do you have any ideas?
Thanks.
update: I can use ODIN to flash other ROMs, but after the flashing process is complete "green passed" light displayed in ODIN, the tablet will not reboot. It hangs at the Samsung splash screen; I've waited about 20 minutes.
Does anyone have any ideas?
Thanks.
dude_48 said:
update: I can use ODIN to flash other ROMs, but after the flashing process is complete "green passed" light displayed in ODIN, the tablet will not reboot. It hangs at the Samsung splash screen; I've waited about 20 minutes.
Does anyone have any ideas?
Thanks.
Click to expand...
Click to collapse
Can you show the ODIN settings please?
Thanks
Thanks for your help Kenora,
Here is my ODIN settings page:
{
"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"
}
As I said earlier, I can't get into recovery mode, but I can flash ROMs with ODIN all day long?
My procedure for ODIN: click AP > choose downloaded .tar file > click start
The ODIN/flashing process seems to be working fine, I get a "green passed" displayed in ODIN every time a flash is completed.
This is the first time I've flashed an Android device, so I'm not sure what is "normal" to be displayed on the tablet after flash completion. Immediately after flash completion, I'm getting an "system update" then an "erasing" immediately after that, then an infinite "Samsung" is displayed.
Is the "erasing" displayed on the tablet normal?
Thanks for your help
UNCHECK "auto reboot" in Odin
Disconnect when flash complete Do Not Turn The Phone On
Reboot into recovery volume up+home+power
Wipe cache/factory rest
Reboot
Thanks for the info Kenora
I tries what you said, but after the flash completed, I still couldn't get into recovery mode.
When I hold down the volume up+ home+ power nothing happens; the tablet is completely unresponsive to those buttons. I pressed them for about 10 seconds, this should be enough, correct?
I can get into download mode like before, reboot that way, but the same thing as before; it hangs at "Samsung"
When I forced it to reboot, "booting recovery" was displayed in the upper left corner; is this normal?
Hold POWER + HOME + VOL DOWN until the screen goes blank then immediately change to VOL UP whilst still holding the other buttons until recovery boots.
Thanks Kenora,
I'm in recovery mode now.
But, I have another question.
Should I select "wipe data/factory reset"
OR
"Wipe cache partition"
dude_48 said:
Thanks Kenora,
I'm in recovery mode now.
But, I have another question.
Should I select "wipe data/factory reset"
OR
"Wipe cache partition"
Click to expand...
Click to collapse
Do both.
Wipe data first then cache i guess just for precaution.
Thanks a lot for your help Kenora,
It's booting now and everything is Good To Go.
Thanks again for your help.
dude_48 said:
Thanks a lot for your help Kenora,
It's booting now and everything is Good To Go.
Thanks again for your help.
Click to expand...
Click to collapse
Ah, its my pleasure.
Just mark the post that is your answer with the tick.
It will help others too figure out the solution too.
Kenora_I said:
Hold POWER + HOME + VOL DOWN until the screen goes blank then immediately change to VOL UP whilst still holding the other buttons until recovery boots.
Click to expand...
Click to collapse
hi ive same Device with Lineage OS 16 rooted on it, i tryied to get to Recovery via the Keys but it gets me to TWRP (custom Recovery) i dont know how to use TWRP 2 flash AP via Odin.. is there a Way? and if not how can i first get back to stock recovery ^^? i dont know how ii could use Odin with TWRP do you maybe?
G
SamsungTabXn1 said:
O to
hi ive same Device with Lineage OS 16 rooted on it, i tryied to get to Recovery via the Keys but it gets me to TWRP (custom Recovery) i dont know how to use TWRP 2 flash AP via Odin.. is there a Way? and if not how can i first get back to stock recovery ^^? i dont know how ii could use Odin with TWRP do you may
Click to expand...
Click to collapse
Go to Download mode and flash the stock rom that way
I tried what you said but when I try to reboot into recovery I get a screen with "installing system updates" which changes to "erasing" before it restarts to eventually hang on the Samsung logo. If I then reboot again, I get an error screen with with a fallen droid with yellow exclamation mark and the text "no command". Is there something I need to do in TWRP before flashing the system ROM so that the tablet can boot into the stock rom's recovery without going through the update first?
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?