Related
Hi all, first time poster, long time reader here. I've gotten many useful info from this forum (updating my 8525, before that, my HP H8315...) and everything has gone without a hiccup, never had a problem since my first PDA phone. However, today as I did a soft-reset on my 8525 (I had Pocket Plus installed, and there's a button to reset). Instead of seeing the usual 3G/ATT screen, there were 4 horizontal bars across the screens. The first bar is red, 2nd is green, 3rd is blue, and last is white. Within the red bar it says:
Herm100
IPL-1.04
Herm100
SPL-2.03
And in the white bar, centered, was the text "Serial"
What's going on? I tried hard-resetting, even taking out the battery, and it still won't boot.
A little background on my PDA phone: I upgraded the ROM a while back, and I also upgraded it to WM6. Nothing was done to it as of recently.
Does anyone know what's up?
Baylenthesky said:
Hi all, first time poster, long time reader here. I've gotten many useful info from this forum (updating my 8525, before that, my HP H8315...) and everything has gone without a hiccup, never had a problem since my first PDA phone. However, today as I did a soft-reset on my 8525 (I had Pocket Plus installed, and there's a button to reset). Instead of seeing the usual 3G/ATT screen, there were 4 horizontal bars across the screens. The first bar is red, 2nd is green, 3rd is blue, and last is white. Within the red bar it says:
Herm100
IPL-1.04
Herm100
SPL-2.03
And in the white bar, centered, was the text "Serial"
What's going on? I tried hard-resetting, even taking out the battery, and it still won't boot.
A little background on my PDA phone: I upgraded the ROM a while back, and I also upgraded it to WM6. Nothing was done to it as of recently.
Does anyone know what's up?
Click to expand...
Click to collapse
Your device seems to be stuck in bootloader mode. Try flashing a current ROM then report.
Hi, thank you for your reply. But I don't quite understand what you meant by "flashing a current ROM"... Can you elaborate further? Thank you!
PS: It is just stuck at that screen forever. Won't even power down or showing a status of it going anywhere. If I lost the sync cable, is there anything else I can do to attempt to revive it or no?
try this
try a factory reset, with the phone off, press and hold the a and b buttons, these are the 2 buttons, 1 just above the windows key and 1 just above the ok key, hold these 2 down and power on the phone while holding them, follow the onscreen instructions, remember this will reset all of your info
Flashing=installing
If you do not have a sync cable d/load and copy ROM from this site and copy it to the sdcard, then install rom from card.
lewnetoons said:
try a factory reset, with the phone off, press and hold the a and b buttons, these are the 2 buttons, 1 just above the windows key and 1 just above the ok key, hold these 2 down and power on the phone while holding them, follow the onscreen instructions, remember this will reset all of your info
Click to expand...
Click to collapse
Hi, thank you for your reply. I tried that and it still went back to the original screen (red green blue white bars).
@Rojam: if I can't use the phone (stuck on that screen) how could I install/run anything?
Thank you very much for all your effort so far.
Great news, I just found out that the sync cable is just a standard USB cable. Now that I found the cable, where do I go from here?
I turned on the device and plug it in. The "Serial" text has now changed to "USB", however, ActiveSync hasn't recognized it yet (Not Connected).
Baylenthesky said:
Great news, I just found out that the sync cable is just a standard USB cable. Now that I found the cable, where do I go from here?
I turned on the device and plug it in. The "Serial" text has now changed to "USB", however, ActiveSync hasn't recognized it yet (Not Connected).
Click to expand...
Click to collapse
Have you Hard SLP'd your device yet? Read the wiki on the Hermes. It will explain how to flash your device. You will either need to connect to active sync or run the file on your SD card. Check to see if the card is formatted corrected per the wiki. You will need to flash a OEM ROM. Hope that helps.
if you have the mini usb cable, connect it to your pc, activesync wont see it because it's in bootloader mode, activesync doesn't need to see it.
Just download another rom and with the phone connected showing the 'bars' screen, run the RUU program to flash the phone from your pc, it'll automatically see the phone, and just flash it, you should be good from there..
yeah, OEM rom for sure
and again, make sure you have HardSPL
Wow, I just want to say THANKS ALOT to everyone attempted to help. Man that was amazing
Anyway back on topic, I have a few questions (I'm kinda slow at these tech things so please bear with me)
1. What kind of ROM (version??, link would be GREATLY appreciated) do I need to flash now?
2. I've read the wiki thing mentioned, but I was not able to see where it shows how to "properly format" my MicroSD card.
3. I haven't "hard SPL" my phone yet (too late now, as it won't boot) so is it safe to flash the ROM? I think the boot-loader screen says my SPL is 2.03 or something (please refer to my original post)
Have same problem w/ my 8525. Plugged in to charger one day and turned on booted up ok. Tried everything before to no avail couldn't get off bootloader screen. Pull out battery to turn off then plug in to charger and turn on should boot properly. I have not been able to get it to boot up properly w/o plugging into a charger 1st. But works fine with this work around. Just make sure don't do soft reset or turn off w/o having charger available or usb cable. Hope works for you.
Mate, find the shipped stock rom. WM06 upgrade should also work as it should recognise the CID. Do a search on the wiki for "stock hermes roms", you might get lucky. Iy doubtful that you will find it on your carriers site now but if you post what your original carrier was you may find some love.
DON'T USE JUST ANY STOCK ROM.... You require the ROM that has the same CID as your original.
If you find the shipped rom, do as HolyAngel said but make sure its the shipped ROM before you put the Hermes into bootloader (tri-colour screen) the click on the RUU program to flash the phone from your pc. I'd also right click on activesync first and go to connections to untick "Allow USB Connection". Less chance of problems that way.
If you get it up and running (saying goodbye to all your contacts, apps and messages), make sure you download and install Hard SPL V7. Makes it easier to fix if stuff like this happens...
Cheers...
Here is the at&t official flasher/installer that I downloaded from at&t for my 8525. This will flash the phone to WM6 and flashes the radio to 1.54.07.00. I changed the location of where the file is uploaded to a place where it should stay for a while. Or you could search for "RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship.exe" that is the name of the official file from at&t
http://www.filedropper.com/ruuhermescingularwwe362502362751540700108uoossvn05ship
ultramag69 said:
DON'T USE JUST ANY STOCK ROM.... You require the ROM that has the same CID as your original.
If you find the shipped rom, do as HolyAngel said but make sure its the shipped ROM before you put the Hermes into bootloader (tri-colour screen) the click on the RUU program to flash the phone from your pc. I'd also right click on activesync first and go to connections to untick "Allow USB Connection". Less chance of problems that way.
If you get it up and running (saying goodbye to all your contacts, apps and messages), make sure you download and install Hard SPL V7. Makes it easier to fix if stuff like this happens...
Cheers...
Click to expand...
Click to collapse
Thank you man, one question: you want me to UNCHECK the "Allow USB connection" ???
WDDPV: thanks man, didn't work, but I appreciate the effort.
Boog: you are the man, thank you!
Downloading the file now, and twiddling my thumbs
No, it didn't work
As I tried to run the RUU that boog provided, I got this message
{
"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"
}
The phone was on, and the "Serial Text" had changed to "USB" before I ran the RUU.
The only other thing I can think of, is trying the at&t stripped rom. I'm being too lazy to search for it right now, but I do know it's in vekyas 4 shared files.
You might be able to choose the bootloader in the xda ruu.
boog321 said:
The only other thing I can think of, is trying the at&t stripped rom. I'm being too lazy to search for it right now, but I do know it's in vekyas 4 shared files.
You might be able to choose the bootloader in the xda ruu.
Click to expand...
Click to collapse
I added the stripped rom, and the official rom links in my sig. Since it seems to be such a popular question.
[CDMA][SPRINT][VZW]P100/P800 GTab Dev Platform AKA UnBrickable Mod && Resurrection
Introduction
I'm not kidding when I say UnBrickable. Modifying the OM pins means you can boot from USB, UART or MMC. This makes the device quite UNBRICKABLE. There is nothing you can do software wise to prevent the device from booting into this mode. We are communicating with the unrewritable, efused IROM on the processor. It's the thing that makes the system on a chip into a "system on a chip".I am here now to tell you how to turn your Samsung P1000 into a KIT-S5PC110 development board. The KIT-S5PC110 development board is the platform used to develop our phones. There are some differences between this mod and the official development platform. The S5PC110 has a removable internal SDCard and no touchscreen.
Why would you want to do this? When you plug in the battery and connect it to the computer in "off" mode, it will become an S5PC110 board awaiting download of a program to run. This occurs long before anything like software or firmware enters the processor. This is the IROM of the device awaiting commands or a power on signal.
How could it possibly be better then JTAG? Let's count the ways....
1. The only part required is a wire.
2. No shipping time.
3. No cost for a box to interface the computer.
4. Permanent.
5. Can be done as a preventive measure.
6. Gives the ability to test new Bootloaders temporarily.
7. Allows development of the entire system.
8. Removes worry about flashing and acts as a backup.
After performing this mod:
Remove the battery, replace the battery, your phone will connect to the computer via USB and await commands. Otherwise it will pretty much act like a P1000. See the Special Instructions section.
Part 1:Hardware Modification
You will need:
1. Get someone who knows what they're doing with a soldering iron. If they don't know what flux is, then they don't know what they're doing. You can send me a PM(or email my [email protected]) or Connexion2005(aka MobileTechVideos.com).
2. Soldering iron - make sure it's sharp, if it's not sharp, then sharpen it, flux it and retin it.
3. Flux
4. Solder
5. Tweezers
6. A relay (possibly- for the wire within to use as a bridge)
7. A #1 tri-blade driver
performing the modification:
1. tear apart your Galaxy Tab... Make sure to take out your SIM and external SDCard before you do this.
1. Remove the two(2) screw covers on the bottom of the unit. Remove two(2) #1 tri-blade screws
2. separate the top cover from the bottom cover
3. Remove eight(8) screws and four(4) connectors securing the board to the unit.
{
"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"
}
4. Remove four(4) screws securing the EMF shield to the board
5. Perform the mod as follows: remove the xOM5 resistor and jumper the non-grounded pad of xOM5 to the same side of xOM0 or xOM3.
6. *OPTIONALLY* hook up UART connections for kernel and/or bootloader debugging at the locations shown in the picture above
7. Reassemble the tab
Special Instructions
This replaces the battery charging sequence. The normal battery charging sequence can be activated by holding power for 4 seconds, then plugging in the device, or you can use an authentic Samsung Charging Cable for charging the battery
To turn on the device, and operate in normal mode, you must hold the power button for 5 seconds.
Part 2: Software Based Resurrection
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer: http://www.java.com/en/download/
The entire software resurrection can be summed up like this
Here is a Galaxy Tab specific video
Unbricking:
1. Apply UnBrickable Mod to your device: see Hardware Modification section
2. Run The Ultimate UnBrickable Resurrector. You can find the Resurrector here in our SVN repository http://code.google.com/p/hummingbird-hibl/downloads/list
When you see this image you are in S5PC110 SEC SoC mode. When you see this mode you must proceed to step 3.
If it will only show this image, then you have not performed the modification correctly, or you have a hardware problem.
If it shows this, regardless of what's on your screen, you're in download mode:
3. Click the Download Mode button (then click the one next to it). I find it's easiest to click Download Mode, type a password, plug in the device, then press enter.
4. Run Heimdall One-Click to flash firmware on your device.
http://forum.xda-developers.com/showthread.php?t=1341666
5. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110 with an OM Value of 29. Now get to developing some serious custom software.
reading material
Creating your own Samsung Bootloaders: http://forum.xda-developers.com/showthread.php?t=1233273
KIT-S5PC110 manual: http://www.mediafire.com/?94krzvvxksvmuxh
how to use DNW: http://tinyurl.com/dnw-how-to
Flash using openOCD and DNW: http://www.arm9board.net/wiki/index.php?title=Flash_using_OpenOCD_and_DNW
another DNW example: http://www.boardset.com/products/mv6410.php
ODroid dev center: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
drivers and utilities
This will be an ever expanding list
Linux Automated UnBricker:http://code.google.com/p/hummingbird-hibl/downloads/list
Windows Drivers http://forum.xda-developers.com/attachment.php?attachmentid=678937&d=1312590673
Windows Download Tool DNW: http://forum.xda-developers.com/attachment.php?attachmentid=678938&d=1312590673
Windows Command Line tool: http://forum.xda-developers.com/showpost.php?p=17202523&postcount=27
Linux DNW Utility: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
Linux ModeDetect tool: http://code.google.com/p/hummingbird-hibl/downloads/list
firmware
Bootloader Hello World by Rebellos http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521
UnBrick tool http://forum.xda-developers.com/showthread.php?t=1242466
You got it working... Great work.
Could you perhaps expand a little more? Such as stating things to avoid to prevent it from bricking? For instance before this mod should a power failure occur when flashing via ODIN = brick. Once this mod is performed. Are there any similar issues?
Wow! very interesting. Makes me want to find a bricked tab.
Sent from my SPH-D710 using XDA App
Awesome job Adam!!! Glad to see the Tab get some unbrickable love!
^^ Thanks
lambstone said:
You got it working... Great work.
Could you perhaps expand a little more? Such as stating things to avoid to prevent it from bricking? For instance before this mod should a power failure occur when flashing via ODIN = brick. Once this mod is performed. Are there any similar issues?
Click to expand...
Click to collapse
You don't need to worry about it. Before your device even starts up, the first thing it does is go into UnBrickable Debug mode and you can boot it into Download Mode from USB. There is no need to worry about anything at all after this. No known firmware can harm your device. You can flash Bada, WP7, just about any bootloader you want, see if it bricks your device... If it does, then just flash back.
If you want, you can flash a Justin Beiber MP3 as a Secondary Bootloader and a LOLCat as a primitive bootloader... You can still recover your device. Just pull the battery out, insert the battery, plug into USB on the computer and click the download mode button.
I am very tempted to do the mod just because I can. Much easier than doing it to my Epic (since I need a working phone) which Adam had added to the list of unbrickables as well
Once again great job on all the unbrickables on the list!
this mod also works on SCH-i800
AdamOutler said:
this mod also works on SCH-i800
Click to expand...
Click to collapse
Adam what about the SPH-P100 SPRINT CDMA model? If it does would it be possible to flash the gsm model version firmware and software onto it? I do not have a sprint account and will not be so I only use it via wifi. Thanks
Sent From My KickAss ATT SGS2 SPORTING CM7
RockRatt said:
Adam what about the SPH-P100 SPRINT CDMA model? If it does would it be possible to flash the gsm model version firmware and software onto it? I do not have a sprint account and will not be so I only use it via wifi. Thanks
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
Yes' but I had problems with the modem, so I did not include it. Check the modem thread for modems.
I just did this mod on my hard bricked vzw galaxy tab, and it saved the hard bricked paper weight to a fully functional tab again. This is definatly a must have mod..
Wondering whether this mod is able to fix a broken/messed up Cache partition ? Thanks
Bro is This method work with GSM galaxy Tab P1000
i hope this work coz i have one in hand when connect to PC show SEC S5PC110 TEST B/d
is that will work in my case ??
ahmed49850006 said:
Bro is This method work with GSM galaxy Tab P1000
i hope this work coz i have one in hand when connect to PC show SEC S5PC110 TEST B/d
is that will work in my case ??
Click to expand...
Click to collapse
I started another thread for P1000 I think. You will need the UnBrickable resurrector and a firmware to flash.
Hi AdamOutler!
I just wanna say thank you, really. I just can't believe my galaxy tab verizon cdma sch-i800 is back and running again.
My hard brick came after i uploaded a wrong bootloader. I thought that i would never see it running again but you made me wrong. So thanks for that again.
I've followed every step you said and now it works.
It was not easy for me though, since i didn't (don't) have soldering skills.
Just for the record, and maybe to help someone else, in my case i've removed the xOM5 resistor and used a wire to make a link with the xOM0 resistor. After making the link between the resistors i've used a tape to keep them together.
Yes, i've used a tape, it's too damn small to use a solder. I know it is not the best option but i reassembled it back and works perfectly now. Ready to try new firmwares again =).
THANK YOU
@AdamOutler Can I apply the mod after a hardbrick has occured? I'm thinking of using the unbrickable mod as a repair method instead of a preventive method as I don't think there is any chance I would hardbrick my tab anytime soon but just in case...
I was just using the phone normally for browsing when it rebooted and after the LG boot splash the phone died (no screen, no lights). I have to take the battery out in order to boot it again but it goes to black screen after splash screen - its not in a boot loop however. I can get into LG's recovery but the only option is to factory reset which I don't want to try yet in case I can recover my data. After searching around for other things to try, I found I can get into Download Mode, however its not detected by LG Mobile Support Tool at this point. When the phone appears dead it actually shows up in windows as 'qualcomm hs-usb qdloader 9008' (not much I can do with this as far as I can tell).
There are lots of threads about the bootloop problem that affected 505xxx serial number devices but mine is 512xxx - only about a year old, so I'm not sure this will be the same thing.
If anyone thinks there is anything I can try to recover files please reply back. I'm going to get in touch with LG support and put the phone in the freezer in the mean time to see if I can boot it after...
Its a hardware issue. They all are.
Every one is its own story but in the end she just wont boot
zeroid said:
I was just using the phone normally for browsing when it rebooted and after the LG boot splash the phone died (no screen, no lights). I have to take the battery out in order to boot it again but it goes to black screen after splash screen - its not in a boot loop however. I can get into LG's recovery but the only option is to factory reset which I don't want to try yet in case I can recover my data. After searching around for other things to try, I found I can get into Download Mode, however its not detected by LG Mobile Support Tool at this point. When the phone appears dead it actually shows up in windows as 'qualcomm hs-usb qdloader 9008' (not much I can do with this as far as I can tell).
There are lots of threads about the bootloop problem that affected 505xxx serial number devices but mine is 512xxx - only about a year old, so I'm not sure this will be the same thing.
If anyone thinks there is anything I can try to recover files please reply back. I'm going to get in touch with LG support and put the phone in the freezer in the mean time to see if I can boot it after...
Click to expand...
Click to collapse
If you like give this test a try. I don't know if it works with a defective mainboard but testing costs nothing..
Download FWUL and boot it (https://tinyurl.com/FWULatXDA).
Then go into the download mode on your g4.
Then open the folder LG in FWUL and open a LGlaf shell.
If you see the prompt in a black terminal ok. If not use the other shortcut with auth in its name. You may have to start the LG laf shell 2 or 3 times sometimes...
If you see the black terminal prompt type in the command:
ls
It should give you a list of files and folders. If not there's something wrong.
If you have luck you can then backup your data.
You need an external SD card to store your data.
I have no access to download mode atm but if you want to test this let me know and I can prepare the rest in a day or 2.
.
Sent from my LG-H815 using XDA Labs
Ok thanks for the offer. I should be able to have a go later today. After I froze the phone for 20 mins it got a bit further - the jingle you get at boot occurred but unfortunately it all died before it got anywhere near my homescreen. Its back in the freezer now.
I'm amazed it can go from working perfectly to a brick instantly, but I guess ifs its a physical connection that is broken on the motherboard...
zeroid said:
Ok thanks for the offer. I should be able to have a go later today. After I froze the phone for 20 mins it got a bit further - the jingle you get at boot occurred but unfortunately it all died before it got anywhere near my homescreen. Its back in the freezer now.
I'm amazed it can go from working perfectly to a brick instantly, but I guess ifs its a physical connection that is broken on the motherboard...
Click to expand...
Click to collapse
You can't fix the mainboard issue by your own. The only chance is getting a replacement by LG.
The freezer method is good for a last backup of your files but don't do it often it is not good for your phone.
.
Sent from my LG-H815 using XDA Labs
Yeah I know, was just hoping to backup a fews things I don't have, SMS messages, some apps configuration that don't sync settings online already....
zeroid said:
Yeah I know, was just hoping to backup a fews things I don't have, SMS messages, some apps configuration that don't sync settings online already....
Click to expand...
Click to collapse
Well then try it with FWUL.
I just need to test the right commands first..
.
Sent from my LG-H815 using XDA Labs
So I got FWUL booted but can't find an LG folder nor LGlaf Shell?
adb devices is working in a terminal.
zeroid said:
So I got FWUL booted but can't find an LG folder nor LGlaf Shell?
adb devices is working in a terminal.
Click to expand...
Click to collapse
Do you have downloaded the latest version? Directly on the desktop?!
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Do you have downloaded the latest version? Directly on the desktop?!
Click to expand...
Click to collapse
I downloaded from the main Androidfilehost link.
Here's the desktop when I boot:
{
"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"
}
Sorry but you haven't downloaded the latest version.
Tbh the sort order by AFH is really misleading and irritating.. so I have just re-ordered the androidfilehost structure so you may find the latest release better now.
The latest one is v1.3 btw.
Go to: https://www.androidfilehost.com/?w=files&flid=142115
Find the folder LATEST
Download FWUL from there
.
OK tried that version, no luck getting the LG LAF terminal window up for the short time the phone stayed in download mode. Even download mode is not stable any more, and just after that it wasn't switching on at all so kind of lost all hope of recovering anything from it now.
Thanks for the link to FWUL - could prove useful in the future.
I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).
{
"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"
}
The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.
So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.
You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.
You can flash other firmware. Find compatible firmware as per your model.
You can disable apps same as you do on android mobile.
My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
zeetotheuno said:
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
Click to expand...
Click to collapse
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
sdancer said:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
Click to expand...
Click to collapse
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
zeetotheuno said:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
Click to expand...
Click to collapse
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
sdancer said:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
Click to expand...
Click to collapse
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
sdancer said:
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
Click to expand...
Click to collapse
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
sdancer said:
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
Click to expand...
Click to collapse
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
zeetotheuno said:
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
Click to expand...
Click to collapse
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
sdancer said:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
Click to expand...
Click to collapse
That's awesome! Thank you in advance.
Yeah, I guess the hardware reset really takes some time and a lot of trial and error.
But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.
To Flash your device,
1) Install the drivers
2) Press Download from SP Flash Tool
2) Connect USB
3) Connect the power outlet from your device (in this case) or connect the battery
****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format
AutoInstall
=================
MediaTek_Preloader_USB_VCOM_drivers.exe
File on MEGA
mega.nz
Manual Install
=================
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
File on MEGA
mega.nz
MediaTek_Preloader_USB_VCOM_Drivers.zip
File on MEGA
mega.nz
Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.
I tried the automatic install and the manual install, but still nothing :/
Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
sdancer said:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
Click to expand...
Click to collapse
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
zeetotheuno said:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
Click to expand...
Click to collapse
Hi
I suppose that this is a driver's problem, you should try to fix it someway.
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
Any idea, Any fix?
paulos2951 said:
Any idea, Any fix?
Click to expand...
Click to collapse
I have no idea bro :/ Hoping that someone will help me
Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
I have the same problem with you
If you find a solution please send me a message !
Jim-Kyritsis said:
I have the same problem with you
If you find a solution please send me a message !
Click to expand...
Click to collapse
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?
Hi.
So.... I ****ed up. I have accidently deleted all internal data on my phone, and I can't use MSMDownloadTool for resetting the phone. As I get the "Sahra Communication error".
I can get into fastboot.
Anyone who has some tips?
zXDexusXz said:
Hi.
So.... I ****ed up. I have accidently deleted all internal data on my phone, and I can't use MSMDownloadTool for resetting the phone. As I get the "Sahra Communication error".
I can get into fastboot.
Anyone who has some tips?
Click to expand...
Click to collapse
I did something similar with the non pro and oneplus replaced the phone, didn't even pay for shipping. Tried every msm tool available. My advice is to open a ticket with oneplus and see what they can do. That being said, my situation was different as it happens weeks after the phone was available (I think I broke it was even available in retail)
So that may have played a huge part of their generosity. I am in the US (may be applicable as well)
That being all said, I never lied to them nor was I looking for a replacement, I just wanted it fixed and assumed I was missing a step that the new phone may have added. I went through every trouble shooting suggestion and even scheduled a remote technician spot.
The technician refused to connect, though, because I downloaded the MSMToolkit he linked to me and said to download and install for it to be available when he remotely connected later. I noticed this technician (who was from germany, oddly enough) sent me a cracked MSMtoolkit (no sign in required like the official one I assumed they would use) the only difference being it was. answer variant the one available to us. So seeing I didn't have to wait for him to initiate it, all I did was attempt it, hoping into at least verify my system drivers were working and that I wouldn't be wasting his time. I replied to him his version was also giving me the error, only in hope he would be better prepared, like maybe it would let him know I needed some special driver or opened port on my network (but it was cracked anyhow)
He replied back in anger " who told you to try? I said to just extract and be ready. we will not assist you further and you are on the hook for any cost of repairs" and then closed my ticket.
I reopened the ticket asking why a technician, who from what I could gather, was a 3rd party service, making such statements on behalf of one plus? I also asked why the same technician was telling me to utilize cracked MSMtoolkits. Next thing I knew I had a next day FedEx label in my inbox to print and ship my phone out.
Maybe it was the timing, the the tech and me calling them out or maybe oneplus can easily fix the problem in house and decided to go that route.
Either way, there's no cost to opening a ticket with one plus, beyond language barriers and tedious preliminary troubleshooting. If you bought it at launch, id be concerned about the length of time and their desire to be as helpful. Not suggesting you lie but maybe just dont over share information.
If you searched, you'd see this :
Completely Bricked! Someone help
One plus 9pr complete brick. Cannot access fastboot or recovery. Will not turn on and when I plug in only shows a connect a chargwer screen. It is charged. I cannot get msm tool to connect either.
forum.xda-developers.com
Make sure you connect the USB cable directly to your computer, preferably in a USB 2.0 port, not via a hub.
Check the other stuff I mentioned in that post too. If you see the sahara communication failure, try rebooting the phone into EDL mode again while the software is running, it'll likely see it the next time. Also make sure you've selected your region in the top dropdown menu in MSM tool.
More info on EDL here : https://www.getdroidtips.com/5-methods-to-enter-edl-mode-on-any-xiaomi-smartphones-qualcomm/
djsubterrain said:
If you searched, you'd see this :
Completely Bricked! Someone help
One plus 9pr complete brick. Cannot access fastboot or recovery. Will not turn on and when I plug in only shows a connect a chargwer screen. It is charged. I cannot get msm tool to connect either.
forum.xda-developers.com
Make sure you connect the USB cable directly to your computer, preferably in a USB 2.0 port, not via a hub.
Check the other stuff I mentioned in that post too. If you see the sahara communication failure, try rebooting the phone into EDL mode again while the software is running, it'll likely see it the next time. Also make sure you've selected your region in the top dropdown menu in MSM tool.
More info on EDL here : https://www.getdroidtips.com/5-methods-to-enter-edl-mode-on-any-xiaomi-smartphones-qualcomm/
Click to expand...
Click to collapse
Not OP, and I truely hope this helps him fix the issue but when this happens to me, I know it wasn't in EDL, as did Oneplus. Thankfully they were open to replacing it for me, but that is nothing to assume ever happening again.
Also had this sahara communication error. Turns out it was just the method of connecting it for me.
What I did was put it into EDL mode with vol up and down for 15s and while holding the keys connect the USB with the software already running, and set to start. I don't remember the message but it said "waiting for communication" or similar, and it would immediately start the recovery when connecting the USB
I recommend this page with some more tips too.. https://www.droidwin.com/fix-sahara-communication-failed-error-msm-download-tool/
Hi
Try to use this tool (credit to craznazn, the developer):
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Set the "Target" button to India, connect your dead phone using vol-up + vol-down + plug in USB, click Start...
I did unbricked LE2120, LE2125 well, using this tool you will get 11.2.4.4, then easily you can find the correct OTA firmware on your choice to be updated locally.
Regards,
xe
{
"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"
}