Database Info

[Q] Bricked TF

Disclaimer: Searching for this brings up far too many results to be useful.
Just attempted a Root of 3.2 using http://forum.xda-developers.com/showthread.php?t=1185104
I'd post this there, but don't have access rights.
Anyways, process went well, rebooted, but once the initial splash screen has cleared, this happens:
{
"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've tried using the same tool to restore to stock, but nothing doing at the moment. Help would be appreciated.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.

How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra

i had the same thing happening to mine when i first rooted to 1.4 prime. however now ive upgraded the rom to 1.6 and so far no artifacts

I had the same problem. I found it was able to fix it by downloading the latest version of the batch script root method zip file and using it to flash my tablet. You need to MAKE SURE you are using the latest version v5 beta5 because the older version had a problem flashing HC3.2 and gave me that error.
here's the link to the forum entry
http://forum.xda-developers.com/showthread.php?t=1185104
here's the link to v5 beta5
http://www.mediafire.com/?59rzqn61jl445lh

Speedstra said:
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
Click to expand...
Click to collapse
I had actually attempted to flash the 3.1 image instead of the 3.2 image. Thus the reason for edit on the original post.
The latest version of the tool should restore it.

EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
Click to expand...
Click to collapse
Please stop using the incorrect term for 'brick.' IT IS NOT A BRICK when your device turns on. Just stop, please.

Just had this same issue, got the same screen - blood pressure went through the roof, had to go water the plants to calm down
I was following this procedure: http://forum.xda-developers.com/showthread.php?p=14760983#post14760983
My mistake was not replacing the boot.img in the root folder with the newer 8659 .img file (linked at the top of the post, but not called out in the otherwise very detailed instructions).
HOWEVER: I did have an issue in that after flashing the wrong .img and getting the "oh sh!t" screen, I could not get adb to list a connected device, which kind of threw me. I could get it into APX mode by holding down the vol-up and power keys (and paying close attention to the "usb connected" notification sound - hold them down for about 10 seconds, hear the "disconnected" sound, then almost immediately hear the "connected" sound and let them go. The screen should stay dark instead of going to the boot logo) and I could see the driver being used, but "adb devices" returned nothing.
So I just ran root.bat again, as I had nothing to lose - and BOOM! Success!
Followed the rest of the procedure with no issues. Hope this helps someone!
Cheers
PatMan

[Q] Bricked SGS4G

Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have this:
{
"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"
}

What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide

Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.

Major kudos to diego930 for such a nicely detailed description of his problem!

Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.

Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!

When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.

ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.

Please help me with "Error! Func NO:12 (FUNC_LOAD_IOM3) Error NO:1"

Hi guys
sorry for my bad English ! but its emergency please help me
my phone is mate7 MT7-L09
after upgrading from 5.1.1 to 6.0 my phone get bricked ! and always display this error :
{
"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 just have access to bootloader (UNLOCKED BOOTLOADER)
please help me , tnx.

If you don't have any important files in your phone, then download firmware 5.1.1 SD card dload folder and press 3 buttons to hard reset
Sent from my iPad using Tapatalk

twlawrenceko said:
If you don't have any important files in your phone, then download firmware 5.1.1 SD card dload folder and press 3 buttons to hard reset
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
i did this ! but my phone wont able to do that because phone dont get charge !
when i connect the charge cable it wont do any act ... i think my phone cant charge ...

pooya2ir said:
i did this ! but my phone wont able to do that because phone dont get charge !
when i connect the charge cable it wont do any act ... i think my phone cant charge ...
Click to expand...
Click to collapse
I had exactly the same experience when attempting to update to 6.0, however my device (TL-10) could charge. You have to get it into fastboot mode. The screen looks very similar to that one (I can't remember the exact button combination, but I think it was Vol+ and power. Then you need to flash stock recovery (if you don't have it already) through ADB commands on your PC.
After that it's merely downloading the correct (full) package and installing it with the aforementioned three-button reset.
Hope this helps!

Scruffykid said:
I had exactly the same experience when attempting to update to 6.0, however my device (TL-10) could charge. You have to get it into fastboot mode. The screen looks very similar to that one (I can't remember the exact button combination, but I think it was Vol+ and power. Then you need to flash stock recovery (if you don't have it already) through ADB commands on your PC.
After that it's merely downloading the correct (full) package and installing it with the aforementioned three-button reset.
Hope this helps!
Click to expand...
Click to collapse
thanks for replay , but my phone cant even charge (
what i must to do ?

pooya2ir said:
thanks for replay , but my phone cant even charge (
what i must to do ?
Click to expand...
Click to collapse
It's a difficult question to ask. If your device still had a decent charge remaining before it crashed and burned you might still want to try to push the wipe / update, regardless of whether it's charging or not.
By the way, there won't be any charging indicators whilst in fastboot / rescue mode, the device will simply just stay on (and warm up a bit).

Google DC unlocker
Sent from my GEM-703L using XDA-Developers mobile app

Nokia 3 stuck in Recovery after a 7.1.1

Hi!
Long time iOS jailbreaker finally moving to Android here.
Just got a spare Nokia 3, brand new.
Updated it from 7.0 to 7.1, than updated to 7.1.1.
Already its stuck in recovery mode due to what seems like a bug with the production line of Nokia? I've seen loose forums about this issue but all guides are either in Hindi or don't actually solve the issue. I just need to ask someone to help guide me through this, since I'm from iOS I'm not very aware about what flashing is, scatter file based flashing ect. I downloaded the base 7.0 from Needrombd.com, also downloaded SmartPhoneFlash Tool since that's meant to help.
I've connected the phone whilst its in fastboot mode, than put the scatter in and clicked download. Takes about 4-6 minutes than instantly hits 100% with a error (pic bellow)
Note: I cannot access the recovery page with the Android mascots chest open, only the screen posted in the reply below.
EDIT: Downloaded OST (Nokia's desktop flash editor), not much help as I can't seem to find the type of file its asking for. Seems like it could be a problem with a com port on the phone side seeing as I've mucked about with other cables/sockets.
Any help is so so appreciated right now :victory:
{
"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"
}

Faraheim said:
Hi!
Long time iOS jailbreaker finally moving to Android here.
Just got a spare Nokia 3, brand new.
Updated it from 7.0 to 7.1, than updated to 7.1.1.
Already its stuck in recovery mode due to what seems like a bug? I've seen loose forums about this issue but all guides are either in Hindi or don't actually solve the issue. I just need to ask someone to help guide me through this, since I'm from iOS I'm not very aware about what flashing is, scatters ect. I downloaded the base 7.0 from Needrombd.com, also downloaded SmartPhoneFlash Tool since thats meant to help but I'm still super lost
I've connected the phone whilst its in fastboot mode, than put the scatter in and clicked download. Takes about 4-6 minutes than instantly hits 100% with a error (pic bellow)
Haven't had a proper phone now for half a week and I'm a little anxious and I just want someone to help me out. Can't wait to finally get into Android!
Any help is so so appreciated right now :victory:
Click to expand...
Click to collapse
Whaat!!! Even with all my experience customising android phones, I haven't had the nerve to try flashing my nokia3 with flashtool. Does your phone still enter download mode? If so I recommend that you flash your phone with OST
You can get more information from this link:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320

redweaver said:
Whaat!!! Even with all my experience customising android phones, I haven't had the nerve to try flashing my nokia3 with flashtool. Does your phone still enter download mode? If so I recommend that you flash your phone with OST
You can get more information from this link:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Click to expand...
Click to collapse
https://imgur.com/sIsqZoo
This is the only thing accessible. Good suggestion though. Seems we have a mystery on our hands.

Note 10 Lite bricked after attempting to install Magisk

I attempted to install Magisk on my stock Note 10 Lite following the official instructions.
As far as I can tell, I did everything right - I made sure to unlock the bootloader and set up the phone again afterwards. Now my phone is stuck in a reboot loop - after holding Vol Down + Power it reboots and goes to the same screen regardless which buttons I hold. The worst thing is that now phone isn't visible to ODIN so I don't know how to proceed or go back to stock. I can't even turn the phone off, thanks non-removable battery! Any tips what to do next or did I buy a $430 paperweight?
{
"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"
}
EDIT: Fixed! What I had to do was:
1. Unplug the phone from the PC, restart the phone by holding Vol Down + Power
2. After the screen goes off, immediately hold Vol Up + Vol Down
3. Plug in the phone to the PC while still holding the buttons (do this quick while the screen is still off)
4. Press Vol Up on the menu to enter download mode
Now I'm back to stock, but at least I can try again doing it differently.

Dang...sorry about that. If you figure something out let us know. Mine is due to arrive tomorrow, hope this isnt going to be an issue across the board....my bad I see you fixed it. Yeah that quick button combo will get you back to download mode[emoji106]
Sent from my SM-N960U using Tapatalk

Follow-up: I managed to install Magisk by following this post: https://forum.xda-developers.com/showpost.php?p=81795603&postcount=2 - the instructions are only partial though, maybe I'll write a guide with links to all the software you need. Then I installed Audio Modification Library and ViPER4Android FX and everything works I'm upgrading from Note 4, so at least I won't lose my favourite audio mods!
If you need some help installing root on yours feel free to send me a DM

thanks sir. .ive been waiting for a guide on rooting this device . .please do so. Ill wait for your post

If I find the time I will write something up as rooting was very easy. But as stated above there are a few steps missing. Zarchiver from play store is a great tool to extract and rename what you need.
Sent from my SM-N770F using Tapatalk

jackmax9999 said:
Follow-up: I managed to install Magisk by following this post: https://forum.xda-developers.com/showpost.php?p=81795603&postcount=2 - the instructions are only partial though, maybe I'll write a guide with links to all the software you need. Then I installed Audio Modification Library and ViPER4Android FX and everything works I'm upgrading from Note 4, so at least I won't lose my favourite audio mods!
If you need some help installing root on yours feel free to send me a DM
Click to expand...
Click to collapse
sooo viper4android IS working? what firmware and android version are you running? I hate to go through the hassle of rooting but I just can't use the stock audio drivers on any phone after trying viper.

Threx71 said:
sooo viper4android IS working? what firmware and android version are you running? I hate to go through the hassle of rooting but I just can't use the stock audio drivers on any phone after trying viper.
Click to expand...
Click to collapse
Yes, it's working for me. It works on all apps (including browser) and all output methods (speaker/wired headphones/Bluetooth).