Database Develop

Dumb, Dumber and me

N900A (AT&T so no custom recovery).
Rom de la Vega worked fine, got root. Loaded some apps, some needing root, some not. Didn't trigger the 0x1, it''s still 0x0.
Everything worked fine until ... well, I don't remember exactly what I did, but it wasn't anything close to "stupidest move ever made". Phone now boots to the Samsung logo with the circles orbiting each other, then goes to the AT&T symbol with a few (about 4) bars of music, and stops. No soft keys (they do flash on for about half a second) and the home key does nothing.
If I wait a few seconds, it reboots, back to the unlocked lock, the "Custom", the Samsung orbits, etc. I assume that's a boot loop.
ADB doesn't see a device. I can boot into recovery (standard AT&T thing), download or standard boot, but ADB doesn't see any device. (The computer is set up correctly - plug my wife's N900A into the same cable and Kies reads it immediately.)
I've tried N900AUCUBMI1_OneClickBin and it seems to run properly, running Odin 3.09 after about 5 minutes. Press Start and the files start downloading. (Port 22, but I''ve learned not to argue with Win7 serial port assignments.) It finishes with all files listed and a green "passed". The pnone boots into the little green guy, then into the boot loop. This is with the original 16GB microSD, a clean 2GB microSD or none at all. I've cleared cache/system or not - same results.
I can't finish the rest of the procedure, because I can't put anything into internal storage - because the computer doesn't see the phone.
I'm at the end of my knowledge. I don't know how things are laid out in Android, so I don't know what to flash or if there's anything I can flash to fix anything.,
Oh - nothing shows on the computer - no Phone and no Card. If USB debug got turned off, I don't know of any way to turn it on from outside. I can't run any Android apps, of course. It I have to, I can install Linux on a partition on this laptop, but is there something I can do to just get back a plain working (preferably rooted) Note 3?
If not, I'm going to have to go back to the big blue and yellow place and feign stupidity, and hope all the boot looping articles will convince them that this is just another one.

You didn't update to the latest MJ 5 firmware, did you? ,accidentally and then try the one click to mi 1?
Sent from my SAMSUNG-SM-N900A using Tapatalk

tdamocles said:
You didn't update to the latest MJ 5 firmware, did you? ,accidentally and then try the one click to mi 1?
Click to expand...
Click to collapse
That's possible. I''ve been looking for links to MI5 and MI9 but with all the deleted links, I haven't been able to find any. All I have is MI1 and the MI9 file with the .tar.md5 files, which I'm reluctant to use, in case I cause a hard brick.

Hard bricked z3c?

Hi All,
I think i have hard bricked my sony xperia z3 compact (d5803).
My z3c had unlocked bootloader, was rooted and run on [ROM][5.1.1|STOCK][D5803|D5833] 23.4.A.1.264 SLiM 4.4, with twrp 2.8.7.0 as bootloader.
Was doing a factory reset when i noticed in twrp that /system wouldn't mount.
Figured there was nothing to lose by doing a fresh flash of the costum rom i was already running, but the "problem" kept existing.
So i thougt there had to be something wrong with the filesystem on /system or that partition got damaged somehow.
After a while searching i found "http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396"
I followed his steps and found out that i needed to set adb in root mode, so i did and was able to transfer the files for "parted". Then i run (as root) the instructions in that post without realizing that i was working at a different device (with of coarse) a different partion table
When i realized that i did a "print" of the partions and did a mkfs on the intended /system partion.
Directly after that i kicked a adb reboot and the device went off, to stay off.
For a compleet log of what i did on adb shell (rooted) see attachment "hard bricked z3c 201512110315.txt" for a little bit cutted version (i tried to cut out the harmless rubisch commands out (first time using adb shell)) see "hard bricked z3c 201512110315 kopie.txt"
At this moment does the device almost nothing to nothing.
When microusb from walloutlet gets pluged in, a quick flash of the charging led (max 1 second) after that its dead.
When powerbutton is pressed with or without microusbcable attached gets no respons.
I have no "Sony" in the screen, and cant seem to reach flashboot mode or flashmode.
Any thoughts on how to fix this?
My first thought was, maybe sony will be able to do a uart flash for me or a motherboard swap. But after calling and explaning them wat i did they dont wanna cooperate even when i'm willing to accept the bill and pay.

Mi3 bootloops, refuses to enter twrp recovery mode

Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!

try to flash official twrp recovery via fastboot

Rahuljs said:
try to flash official twrp recovery via fastboot
Click to expand...
Click to collapse
How to flash it ?? Method pls...
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!

Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?

Try flashing the phone via MIUI flashing tool as you were able to access fastboot mode
http://en.miui.com/a-234.html

xypherize said:
Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!
Click to expand...
Click to collapse
Here is the link for tutorial for flashing recovery via fastboot mode. All commands are same just download the twrp recovery image from here. DON'T FORGET TO RENAME THE IMAGE FILE, BECAUSE ADB DOESN'T RECOGNISE ANY SPECIAL CHARACTER.

what did you do ? I'm stuck in the same situation word by word.
did you solve this issue ?

yohaneseko said:
Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?
Click to expand...
Click to collapse
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.

Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
rxl.noir said:
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.
Click to expand...
Click to collapse

yohaneseko said:
Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
Click to expand...
Click to collapse
Heyaa~
For the battery, you could easily found it on Tokopedia started from 110k, although most of them are shipped from Jakarta. The replacement process is quite easy, you might only need #0 Phillips or any small plus screwdriver, a plastic card (for spudge replacement), and some guts :q. The details and steps are on my prev. post.
I haven't tried to sent it to the seller/distributor, since it might take a long time to get it done.

Just a little update;
I replaced my battery on my Mi3 that have the same exact case as yours, and it finally works. No more short bootloop, no more stuck in fastboot.

How can I backup data partition of phone with broken screen?

Ok so I have a samsung galaxy xcover 3 with a broken screen. The phone itself works, however the screen is cracked up so badly that the LCD matrix is broken. There is some data I need to get off that phone for the owner of the device. Is there a way to get the data partition? I have a lot of experience installing custom roms on samsung devices. So I tought I would just blindly install twrp with odin and create a backup through twrp and pull it off the sd card. Would that be possible? Is there a better/easier solution?
P.s.: USB debugging is disabled so doing anything with ADB through the system is pretty much out of the question.

{LOS 17.1.5} Big problem : touchscreen unresponsive on System, but works on TWRP

Hello All
Sorry to bother you again with my troubles.
My xz1 compact (with LOS 17.1.5 last version of OS , Sony Firmware .228) wasn't charging battery anymore last night (no way to make it charge) , and went off out of battery. I dissasemblied it to check and clean the charging port, and the current came back and charged the battery full. But after reassembly the phone booted and stay stucked on start screen with unresponsive screen.
No way to unlock, no response of the touch screen, no ADB operation possible as the phone was "unauthorized" in the terminal window. .
I went rebooting on TWRP recovery to back up my files, and there the screen worked perfectly ! i could do my backups, wipe everything and reinstall LOS 17.1.5, but again on startup the touchscreen is away !! ... the touch screen looks fully functional when on TWRP, could it come from a software or hardware issue on my phone ? .
Someone in my city told me that I've could have boken one small resistors near to the screen connector on motherboard, but I can't see anything when comparing to the motherboards images
Bye and thanks for your help.

It's incredible, as I can perfectly manage the phone on TWRP recovery app, but no way to do anything on screen when a system is booted

Hello all, still trying to fix that problem... After full wipe and formatting (via TWRP, screen is working on it), and reinstall of LOS I get system to boot, but with black screen, the phone react to button press (power and volume), but no to any screen command . Is there a way to test services and perpiherals with TWRP ? Tryed to move back to sony stock firmware .228, but with bootloader unlocked it's not possible. Thank for any hint or suggestion, bye.

seven hole said:
Tryed to move back to sony stock firmware .228, but with bootloader unlocked it's not possible
Click to expand...
Click to collapse
I'm running .228 with an unlocked bootloader. If the flashtool or Newflasher isn't working then you need to use Sonys TOOL. As for your main issue, I have no idea, it is strange though.

SXUsr said:
I'm running .228 with an unlocked bootloader. If the flashtool or Newflasher isn't working then you need to use Sonys TOOL. As for your main issue, I have no idea, it is strange though.
Click to expand...
Click to collapse
Thank you @SXUsr yes it is a strange issue, as the screen works with TWRP, and the hardware looks no faulty .. my only clue is that I've touched and clean the Charging port to cure a bad connection ( and it's charging directly now )
I will try to reinstall Sony .228 from newsflasher or Sony "Emma" tool (thanks a lot for the link I couldn' find it by research) and I will maybe know if it's a soft or hardware issue !

Firmware .228 reinstalled from newsflasher . the screen seems to work .. the telephone is still with bootloader unlocked ... Now I'm back on ungoogling it . Thanks