I have an issues with the Virgin Telly Tablet. I'm stuck on the Google Verification page. II bought this cheaply from eBay so have no access to linked Google account. I tried to get the tablet into fastboot mode to unlock bootloader but it didn't work.
Regardless what I try I am stuck with the same output:
FAILED (remote: 'Unlock operation is not allowed')
This is the output for fastboot getvar all:
.
.
.
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: JOYASZ8783_TTB_C_N
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
I have spent the last 2 days trying to get it reset to factory setting with no success. I then stumbled across a guide in this forum and decided to give it a go.
I am stuck with the first step as SP flashtool fails to communicate with tablet. I have installed MTR drivers etc and windows device manager seems to detect it so shouldn't be a USB driver issue. Any new ideas to help are welcome. I am fairly new to this but love tackling problems of this nature.
ZiAndoid said:
I have an issues with the Virgin Telly Tablet. I'm stuck on the Google Verification page. II bought this cheaply from eBay so have no access to linked Google account. I tried to get the tablet into fastboot mode to unlock bootloader but it didn't work.
Regardless what I try I am stuck with the same output:
FAILED (remote: 'Unlock operation is not allowed')
This is the output for fastboot getvar all:
.
.
.
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: JOYASZ8783_TTB_C_N
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
I have spent the last 2 days trying to get it reset to factory setting with no success. I then stumbled across a guide in this forum and decided to give it a go.
I am stuck with the first step as SP flashtool fails to communicate with tablet. I have installed MTR drivers etc and windows device manager seems to detect it so shouldn't be a USB driver issue. Any new ideas to help are welcome. I am fairly new to this but love tackling problems of this nature.
Click to expand...
Click to collapse
@ZiAndoid
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
Related
Code:
fastboot oem get_unlock_data
...
(bootloader) 3A95030165469753#5A583142333336
(bootloader) 35325A00585431303232000000#7214
(bootloader) 61084A7E89A8BD2716AC06BEAD4EA6E
(bootloader) DC583#1A7AB40312000000000000000
(bootloader) 0000000
OKAY [ 0.281s]
Received no e-mails from their side..
Checked spam folder too..
It hardly takes a few minutes. Might be something on Moto's servers.
Request again.
Tapped from My Moto X
neo.ank said:
It hardly takes a few minutes. Might be something on Moto's servers.
Request again.
Tapped from My Moto X
Click to expand...
Click to collapse
Trying since 2 days
I get your unlock key
UVEI4OFPJRIZUD6RN2WE
here is your unlock key....my device is showing that it is not qualified...see if u can get my unlock key here is my code..
3A55640206602954#5A58314233323439384200585431303232000000#7CB38EF02F495B40ED4A135B509807FC5E701F99#D5E1E701120000000000000000000000
please help to generate my unlock code
9900054551989100#5441303035304145494300585431353238000000#41236E650F9A7B9C7293E891862BFFE2163EA14C#E2375A0F000000000000000000000000
Hi,
I've been tricking around with the Note 4 64gb since it entered into a Bootloop about 2 weeks ago and at one stage I got into a Chinese Rom but then it all fell apart. I cannot even get back to that point.
Phone will not switch on, will not enter into the phones ROM so I cannot change any of the settings within. Therefore the bootloader remains locked because I cannot access the phone however I know I can flash to the phone but why it will not restart is beyond me. Remains on Miui Screen on constant reboot after 30 seconds or so.
When I did get the CN Dev Rom(whatever it was as I got excited when it loaded and cannot remember how I did it) to load it was the phone disconnected from USB and below the powered by android came up. It would only go passed this when I connected the USB to power/pc as apparently the battery is bad. I know this couldn't be the case because the phone will happily sit for hours in Fastboot Mode(Rabbit) so maybe that Rom affected the hardware badly.
Using Smart Phone Flash Tool I can get
6.12 Global, 8.03 Global, 7.12 CN and 8.1.18 Roms to flash to the phone without any success of booting up normally or even showing the powered by android thing. These will all only work with the Cust.img file because otherwise it says File Too big.
It only flashes with everything ticked except preload. It will not work just by having system and boot selected. Error Codes are then 0Xc00500003
Using Mi Flash I can see the device connected in Fastboot mode and it says Flash Complete but the fact it only takes 1 second leads me to believe it does not actually flash anything because it won't reboot.
Using ADB and entering command with admin rights and typing adb devices(whilst in fastboot) doesn't show the device connected at all but refreshing Mi Flash does show the device. Very odd.
When I did get the Chinese Dev Rom to work on the phone I did notice that the IMEI had been wiped from the phone which was less than helpul also.
Can anybody help me get the phone back to a working state?
Thanks in advance
I think the fact you are not getting no reply from 'adb devices' is not a good start, are you sure you have all the correct drivers? Secondly do you have another computer to try it on?
Here is the minimal ADB:
http://xiaomitips.com/download/adb-setup-v1-4-3/
Here is the Unbrick Guide & install the drivers that are in it:
http://forum.xda-developers.com/red...redmi-note-4-unlock-bootloader-t3517806/page5
Wilderone said:
I think the fact you are not getting no reply from 'adb devices' is not a good start, are you sure you have all the correct drivers? Secondly do you have another computer to try it on?
Here is the minimal ADB:
http://xiaomitips.com/download/adb-setup-v1-4-3/
Here is the Unbrick Guide & install the drivers that are in it:
http://forum.xda-developers.com/red...redmi-note-4-unlock-bootloader-t3517806/page5
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. At the time of your reply I am still fighting with the phone.
I have managed to get CN Dev back working again and I'm back to having No IMEI. It seems I may have wiped it during the earlier flash attempts.
Problem now is the people who gave me the phone to fix(family) threw out the box so I don't have the IMEI to reapply to the unit. Damn
Cannot then get Miui Account to load in because the phone won't confirm IMEI information.
Also battery running on CN is totally dead when running the OS. As soon as you pull the USB it powers down yet, like I said before, when not in ROM could happily reboot all day long or sit on the Fastboot screen.
Sounds like it may have wiped all your Engineering settings? just a guess, I'm assuming it's brand new so its strange that it has a battery problem?
As for the IMEI I just happen to have saved some links from the en.miui forums just in case I ever came across this problem but....you will need a valid IMEI.
http://en.miui.com/thread-411112-1-1.html
http://en.miui.com/thread-474409-1-1.html
Sent from my Redmi Note 4 using Tapatalk
The Device is basically brand new. Turned on Christmas Day by Nephew. I turned it on a few weeks before it and downloaded everything etc and did the updates. I don't think he would have been tinkering with ROM(all of them are not technically adept) and it wasn't damaged by all accounts .
Anyway. I've managed to Harvest an IMEI from an Old Phone, Installed this through a programme, connected my Mi Account, unlocked the bootloader and then flashed the correct Global Rom. Excellent.
No. The Battery is now the issue. It will not charge.
This is what I now need advice on. Anything I can do to get around this? Battery Hardware Tests say it's fine but It's not charging and only working on USB power.
What does your battery log look like?
Dial *#*#3646633#*#*
Sent from my Redmi Note 4 using Tapatalk
Aha, I see one major difference. I'm not showing a Battery Voltage
Battery Status: Charging (USB)
Battery Level: 0
Battery Scale: 100
Battery Health: Good
Battery Voltage: 0 mV
Battery Temperature: 37.0c
Battery Technology: Li-poly
Time since Boot: 31:00(not that it matters)
Interval of Info Record[1-100] 10 is in the changeable box
Battery Info Record: Start
--------------------------------------------
I'm going to surmise that the Voltage is the Problem here.
So its detecting the battery & health is good but at 0% & has no voltage lol.
What about under Hardware Testing/ Power/Charge Battery
Anyone can chime in here please as I'm not an electrician.
FYI, This was taken when I was plugged in.
Sent from my Redmi Note 4 using Tapatalk
Battery on USB and Battery with Original Charger plugged into wall outlet returns the same 0v Voltage.
When I plugged the device into the Wall and powered up it said 50% battery and within a second said 0% Battery and back to square One.
Im not sure what that means sorry, If it were me, in the predicament with your warranty I would be inclined to open it up & remove the battery for a while.
Depends if you are technically minded although it doesn't look too difficult.
https://youtu.be/6RBHqqF2Cg4
Failing that I would look on AliExpress for a new battery & see if it is worth the time & effort.
Also you may post some of this elsewhere in other forums to see if you can get an expert opinion.
Sent from my Redmi Note 4 using Tapatalk
Replaced battery. No luck. So it wasn't the battery.
BertieBaron said:
Replaced battery. No luck. So it wasn't the battery.
Click to expand...
Click to collapse
Sounds strange for a new device but it is possible it's developed a hardware problem.
I'm assuming you have tried different chargers, cables & had a physical look at the micro USB port for any signs of damage.
Have you had a good research on Google?
I found the following:
https://www.androidpit.com/how-to-fix-a-phone-that-won-t-charge
https://www.google.com.au/search?hl...rki9AO&gws_rd=ssl#gfe_rd=cr&gws_rd=ssl&xxri=1
See how you go & let me know.
Sent from my Redmi Note 4 using Tapatalk
Have I researched Google? Yes, many times every single day.
I did check and rub over the USB port to ensure that the connections should be fine and straight etc.
When I run a test on "Charger Plug In" using *#*#36443#*#* I can see Charger Current: Fluctuating between - numbers and 250mA so there's power coming from the USB Port into the Phone.
Using *#*#3646633#*#* I can see the Battery but without Voltage going into it.
Is the problem somewhere between power coming into the phone and getting to the battery?
When I removed the battery the phone will not power up by itself connected to AC Power
BertieBaron said:
Hi,
I've been tricking around with the Note 4 64gb since it entered into a Bootloop about 2 weeks ago and at one stage I got into a Chinese Rom but then it all fell apart. I cannot even get back to that point.
Phone will not switch on, will not enter into the phones ROM so I cannot change any of the settings within. Therefore the bootloader remains locked because I cannot access the phone however I know I can flash to the phone but why it will not restart is beyond me. Remains on Miui Screen on constant reboot after 30 seconds or so.
When I did get the CN Dev Rom(whatever it was as I got excited when it loaded and cannot remember how I did it) to load it was the phone disconnected from USB and below the powered by android came up. It would only go passed this when I connected the USB to power/pc as apparently the battery is bad. I know this couldn't be the case because the phone will happily sit for hours in Fastboot Mode(Rabbit) so maybe that Rom affected the hardware badly.
Using Smart Phone Flash Tool I can get
6.12 Global, 8.03 Global, 7.12 CN and 8.1.18 Roms to flash to the phone without any success of booting up normally or even showing the powered by android thing. These will all only work with the Cust.img file because otherwise it says File Too big.
It only flashes with everything ticked except preload. It will not work just by having system and boot selected. Error Codes are then 0Xc00500003
Using Mi Flash I can see the device connected in Fastboot mode and it says Flash Complete but the fact it only takes 1 second leads me to believe it does not actually flash anything because it won't reboot.
Using ADB and entering command with admin rights and typing adb devices(whilst in fastboot) doesn't show the device connected at all but refreshing Mi Flash does show the device. Very odd.
When I did get the Chinese Dev Rom to work on the phone I did notice that the IMEI had been wiped from the phone which was less than helpul also.
Can anybody help me get the phone back to a working state?
Thanks in advance
Click to expand...
Click to collapse
HI there. i have mi note 4 which is currently stuck on bootloop.can u tell me please how to boot up this device.i have done almost everything.my phone's condition is just like yours.
tahir786 said:
HI there. i have mi note 4 which is currently stuck on bootloop.can u tell me please how to boot up this device.i have done almost everything.my phone's condition is just like yours.
Click to expand...
Click to collapse
Your model is Redmi Note 4, right?
Which variant? The one with MediaTek chipset or the one with Qualcomm chipset?
BubuXP said:
Your model is Redmi Note 4, right?
Which variant? The one with MediaTek chipset or the one with Qualcomm chipset?
Click to expand...
Click to collapse
its a Qualcomm.
Hello
I received brand new Xiaomi Remi Note 4 (MediaTek) yesterday and I opened the package and wanted to boot the device up and I was shocked that the device is hanging on Mi logo and then restart or it does what known bootloop, the device enters fastboot mode and nothing else, I tasted the device with too many tools and methods so finally I made sure that there is a problem in internal storage or (eMMC) the data stored as RAW data as shown in the following result:
[VKZ5H6QKR4GEC6TC] *** Fastboot mode
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-sizetp: 2b00000
(bootloader) partition-typetp: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1b000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cust: 20600000
(bootloader) partition-type:cust: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 400000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 400000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:scp2: 100000
(bootloader) partition-type:scp2: raw data
(bootloader) partition-size:scp1: 100000
(bootloader) partition-type:scp1: raw data
(bootloader) partition-size:md3img: 500000
(bootloader) partition-type:md3img: raw data
(bootloader) partition-size:md1arm7: 300000
(bootloader) partition-type:md1arm7: raw data
(bootloader) partition-size:md1dsp: 400000
(bootloader) partition-type:md1dsp: raw data
(bootloader) partition-size:md1img: 1800000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect2: d78000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: 800000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: nikel
(bootloader) version-preloader:
(bootloader) version: 0.5
I was able to repair system, userdata and cache partitions but that was useless, I'm not sure that the problem could be fixed by software solution or hardware one or it's initially and technical problem
Any one can post working bootloader log here using the command 'fastboot getvar all'
tahir786 said:
its a Qualcomm.
Click to expand...
Click to collapse
The bootloader is locked or unlocked?
BubuXP said:
The bootloader is locked or unlocked?
Click to expand...
Click to collapse
sadly,bootloader is locked.....
---------- Post added at 10:01 AM ---------- Previous post was at 09:55 AM ----------
BubuXP said:
The bootloader is locked or unlocked?
Click to expand...
Click to collapse
it is locked ...is there any way to wake that device up...when i connect that phone via edl mode in mi flashtool ,it always flashing such **** like hello packet and nothing happns..,,, and when i connect via fastboot it took about a second and success showing but nothing happens... plzzz tell me what should i do??
tahir786 said:
it is locked ...is there any way to wake that device up...when i connect that phone via edl mode in mi flashtool ,it always flashing such **** like hello packet and nothing happns..,,, and when i connect via fastboot it took about a second and success showing but nothing happens... plzzz tell me what should i do??
Click to expand...
Click to collapse
There is a solutions. You must open your phone to remove the battery, then you need to cut a USB cable to modify it.
If you are capable of this I can explain the procedure.
Hi everyone,
Im a new user here and this is my first post so I hope you guys could help me,
I have an Genuine Htc one m7 google play edition, never unlocked and never rooted and with S-ON, it's not starting, I'm trying to fix this for a couple of weeks but had no success, after updating to kitkat my phone just restarts two times and then shows the android logo with a triangle.
I googled this problem for weeks now and I haven't found any solutions in some forums they said that this problem can't be fix right now but maybe google will release a patch to fix this.
I can not unlock the bootloader,
I can not S-off
I can not even flash a recovery like twrp
I tried to unlock via ADB no success
The Errors:
trying fastboot oem unlock, result:
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.405s]
finished. total time: 0.414s
I'm stuck here I don't know what to do
PLEASE GUYS HELP.
:crying::crying::crying::crying:
RoyalShala said:
Hi everyone,
Im a new user here and this is my first post so I hope you guys could help me,
I have an Genuine Htc one m7 google play edition, never unlocked and never rooted and with S-ON, it's not starting, I'm trying to fix this for a couple of weeks but had no success, after updating to kitkat my phone just restarts two times and then shows the android logo with a triangle.
I googled this problem for weeks now and I haven't found any solutions in some forums they said that this problem can't be fix right now but maybe google will release a patch to fix this.
I can not unlock the bootloader,
I can not S-off
I can not even flash a recovery like twrp
I tried to unlock via ADB no success
The Errors:
trying fastboot oem unlock, result:
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.405s]
finished. total time: 0.414s
I'm stuck here I don't know what to do
PLEASE GUYS HELP.
:crying::crying::crying::crying:
Click to expand...
Click to collapse
Any one pleaseee
I am trying to unlock bootloader of my MotoG5s plus (XT1804) but had no luck
Everytime I use command: fastboot oem get_unlock_data,
I get following error message: (bootloader)Unlock Data Unavailable.
I have checked OEM unlocking and USB Debugging but problem still persists.
Also, I have been gone through Motorola forms and google but got no solution.
When I use fastboot getvar all I get, (bootloader) cid: 0x0000
Please Help:crying:
Any Help would be appreciated:angel:
P.S.: I still posted my problem at Motorola page
Here for more details:
Message Number: 4549
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/4131133/highlight/true#M9174
SuperSaket said:
I am trying to unlock bootloader of my MotoG5s plus (XT1804) but had no luck
Everytime I use command: fastboot oem get_unlock_data,
I get following error message: (bootloader)Unlock Data Unavailable.
I have checked OEM unlocking and USB Debugging but problem still persists.
Also, I have been gone through Motorola forms and google but got no solution.
When I use fastboot getvar all I get, (bootloader) cid: 0x0000
Please Help:crying:
Any Help would be appreciated:angel:
P.S.: I still posted my problem at Motorola page
Here for more details:
Message Number: 4549
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/4131133/highlight/true#M9174
Click to expand...
Click to collapse
yaaa mee tooo
Hello everyone, sorry if i'am on the wrong section.
After doing a system update (4.4.4 to 5.0), my Moto G 1st Gen (Falcon) xt1033 get a hard brick and died. No power up, no charging also. No one life signal.
Searching here on xda i find some tutorials to revive the phone from the "Bulk mode". I got it recover the fastboot bootloader, but it seems corrupted . First, on his init, shows: "Failed to initiate partition table" .. after, i cant access no one of the options (displays "boot up failed").
I can't flash to stock using fastboot on windows (gives "Permission denied" or "remote failure") because i can't unlock the bootloader --- and i can't unlock the bootloader because i can't enable "oem unlock" on 'developer options'.
Above the 'fastboot getvar all' command:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A(*)
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Samsung REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: af62b68a
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 1F7CED030F000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git:
(bootloader) sbl1.git:
(bootloader) rpm.git:
(bootloader) tz.git:
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.063s
Any ideas? (other than throwing in the trash)
Thank you all.
joaoporto said:
Hello everyone, sorry if i'am on the wrong section.
After doing a system update (4.4.4 to 5.0), my Moto G 1st Gen (Falcon) xt1033 get a hard brick and died. No power up, no charging also. No one life signal.
Searching here on xda i find some tutorials to revive the phone from the "Bulk mode". I got it recover the fastboot bootloader, but it seems corrupted . First, on his init, shows: "Failed to initiate partition table" .. after, i cant access no one of the options (displays "boot up failed").
Any ideas? (other than throwing in the trash)
Thank you all.
Click to expand...
Click to collapse
Don't worry my friend the problem can be solved tomorrow I will prepare all what you need to bring your device back to life stay updated ....
The first rule of success: NEVER GIVE UP!
Teddy Lo said:
Don't worry my friend the problem can be solved tomorrow I will prepare all what you need to bring your device back to life stay updated ....
The first rule of success: NEVER GIVE UP!
Click to expand...
Click to collapse
Thank you so much, i appreciate that. You are my only hope.
joaoporto said:
Thank you so much, i appreciate that. You are my only hope.
Click to expand...
Click to collapse
Hi friend , here you go
https://forum.xda-developers.com/android/help/guidy-to-unbrick-hard-bricked-moto-g-t3875035
Let me know if you fixed or not .
Good luck . With Respekt Teddy Lo
Teddy Lo said:
Hi friend , here you go
https://forum.xda-developers.com/android/help/guidy-to-unbrick-hard-bricked-moto-g-t3875035
Let me know if you fixed or not .
Good luck . With Respekt Teddy Lo
Click to expand...
Click to collapse
I was able to exit QHSUSB_BULK and start the fastboot bootloader. The problem is that I can not do anything else after that. fastboot does not accept any commands.
joaoporto said:
I was able to exit QHSUSB_BULK and start the fastboot bootloader. The problem is that I can not do anything else after that. fastboot does not accept any commands.
Click to expand...
Click to collapse
Can you make some short video about the problem and post on Youtube ?
Teddy Lo said:
Can you make some short video about the problem and post on Youtube ?
Click to expand...
Click to collapse
MAN, YOU WILL NOTE BELIVE.
I had already done a unbrick tutorial like yours. but i've tried with your files and "it worked". a lot of errors has show up on cmd but like magic the phone have displayed the unlocked bootloader logo, the motorola logo and the first configuration page. after that, the phone restarted alone and get into a loop, restarting always after motorola logo. but even so, the device is unlocked and alive. Now i can flash the appropriate stock rom. Thank you so much, you saved my phone.
EDIT:
I tried flash the stock rom 4.4.4 that i have here on my PC, but now the loop are in bootloader unlocked screen. i installed the twrp and looked at the log. shows:
"Failed to mount '/data' (invalid argument)"
"Failed to mount '/system' (invalid argument)"
EDIT2:
I was able to remove the error messages in the twrp log. it just repair system and data in twrp-wipe. after that I tried the flash with another stock rom 4.4.4 and now everything is working normally. Very happy with my phone resurrection.
Well done my friend , be carefull next time ....
Help...
My old moto G1 is not turning on or not charging. When i connect to charger, only the white led light are on. No keys are working. Not able to turn on or go fastboot.
Anyone got a solution?
tomin01 said:
Help...
My old moto G1 is not turning on or not charging. When i connect to charger, only the white led light are on. No keys are working. Not able to turn on or go fastboot.
Anyone got a solution?
Click to expand...
Click to collapse
Hi, when you say old probably it was drained the battery so to fix the problem what I suspect that the battery is 0% you need charger with little bit more Ampers like an original charger for Samsung 5v and 2A so put the cell phone on that charger for about 2-3 hours and if is that the problem it will be fixed. Good luck
Teddy Lo said:
Hi, when you say old probably it was drained the battery so to fix the problem what I suspect that the battery is 0% you need charger with little bit more Ampers like an original charger for Samsung 5v and 2A so put the cell phone on that charger for about 2-3 hours and if is that the problem it will be fixed. Good luck
Click to expand...
Click to collapse
The phone was shut down with 70 percent battery. Not drained completely. Plugged with pc, different chargers and still no luck. In service centre, they replaced the battery and still it not turning on. They told that it's not a board complaint and they don't know to fix it.
The phone was with cyanogen mod 13.
tomin01 said:
The phone was shut down with 70 percent battery. Not drained completely. Plugged with pc, different chargers and still no luck. In service centre, they replaced the battery and still it not turning on. They told that it's not a board complaint and they don't know to fix it.
The phone was with cyanogen mod 13.
Click to expand...
Click to collapse
Service center doesn't know how to repair it? Then probably is some problem with your mainboard, but try to connect your device with PC and see if is somehow recognized if not probably is some hardware problem.
Teddy Lo said:
Service center doesn't know how to repair it? Then probably is some problem with your mainboard, but try to connect your device with PC and see if is somehow recognized if not probably is some hardware problem.
Click to expand...
Click to collapse
Thanks sir. I'll try. In our locality they do the worst service. You will hate it, when you go to service centre here. They replaced a battery infront of me and plugged it to charger and only the led light was on. They told me they don't know the reason and if I agree they will change the motherboard and will cost 70 percent of phone price. Connecting to pc didn't recogonized. Phone is dead. Only led lights. I removed the battery and connected directly to power supply and then also only led is on.