Related
Hi there!
I have a Galaxy Tab 7 and I am a noob on this development stufs.
I am trying to install this version on it:
cafe-ti.blog.br/1835~samsung-galaxy-tab-7-gt-p1000-android-jelly-bean-cm10
And looks like the language is pretty simple but I have no clue how to do it...I mean, I trie using Odin..did not work...
I tried this instead:
[wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(P1000L):_Full_Update_Guide
but the Recovery mode does not work!
There is any step by step non expert language tutorial to how let the Tab 7" with the CM10?
Thanks from Brazil
Rafael
You try this?
http://forum.xda-developers.com/showthread.php?t=1542897
orangekid said:
You try this?
http://forum.xda-developers.com/showthread.php?t=1542897
Click to expand...
Click to collapse
My one is the 7", not the 7'7" and its the GT-P1000L..
It will work on it?
rafapiloto195 said:
My one is the 7", not the 7'7" and its the GT-P1000L..
It will work on it?
Click to expand...
Click to collapse
I tried this video, passin to 2.3.6 first, using Odin..
youtube.com/watch?v=fXDvq5SaA70&feature=relmfu
workd well, however, after flashing, is not turning on again...
What may can be?
Oh yeah don't use the 7.7 forum then...
You Odin flashed a ROM and now the device won't even turn on? Or is it just boot loop?
orangekid said:
Oh yeah don't use the 7.7 forum then...
You Odin flashed a ROM and now the device won't even turn on? Or is it just boot loop?
Click to expand...
Click to collapse
There is no sign...does not even turn on...
black screen only..nothing...
rafapiloto195 said:
There is no sign...does not even turn on...
black screen only..nothing...
Click to expand...
Click to collapse
Can you link the ROM you Odin flashed?
Sounds like you bricked your device...
edit: if you plug it into your computer does anything pop up on the computer?
orangekid said:
Can you link the ROM you Odin flashed?
Sounds like you bricked your device...
edit: if you plug it into your computer does anything pop up on the computer?
Click to expand...
Click to collapse
I had to come to work and let it at home...
Well, as berfore flash it I let the USB on the debugging, I will track the oneclick root directly to se if at least will get a conecction with a computer;
I will try to send it to the dealer as well.
I believe as I let it on the 2.3.6, wich is the same one running on Kies, still under warranty to perform a hard brick recovery.
Let's see.
Thanks..I'll keep you guys posted.
Yeah let us know, hopefully we can do something, not sure why a GB Stock Odin flash would brick it.
orangekid said:
Yeah let us know, hopefully we can do something, not sure why a GB Stock Odin flash would brick it.
Click to expand...
Click to collapse
Just replying to your question, I flash it with the one on the youtube video link I posted:
www.youtube.com/redirect?q=https://...yuzT76vVlfj4vSE98MTM0ODM0OTI1NUAxMzQ4MjYyODU1
rafapiloto195 said:
Just replying to your question, I flash it with the one on the youtube video link I posted:
www.youtube.com/redirect?q=https://...yuzT76vVlfj4vSE98MTM0ODM0OTI1NUAxMzQ4MjYyODU1
Click to expand...
Click to collapse
Well, looks like it is working again,
however, when I try to turn on on the recovery mode to wipe data,
it shows E: MBR Checksum error
Internal MMC checksum verify failed.
Any ideas?
great idea
+1 orangekid
asdera-and said:
+1 orangekid
Click to expand...
Click to collapse
Ok! Is on the 2.3.3 now.
I want to put the Cyanogen 4.1.1 as described here:
http://forum.xda-developers.com/showthread.php?t=1871113
However, when I tried it shows me the error I mentioned above and also
Failed to verify whole-file signature...
Then , I was able to come to CMW where I should install the Cyanoi 4.1.1 however keeps showing me the error:
E: Can't moun /emmc/
Ideas?
OK
now I tried this room:
Rom: Overcome + Overcome Kernel
Following the guide step by step and then the E: looks like to be damaged. I can not even turn it on again.
Just when I put it to charge, it will show the brick scree (the fone and the computer)...
I am almost givin up...
Does your tab have an SD card in it?
If so try a different one, if not odin 100% stock, then do the root, and ROM flash again.
Hello XDA developers!
I hope you can help me with a serieus problem on my Nexus5 Device!
Let's tell you my little adventure with my Nexus5 :
First my Nexus5 Device worked perfectly, but then the radiobaseband and the sensors magically dissapeared!
https://db.tt/cdZiSukZ i've tooked some screenshots of it on dropbox.
Then I Flashed the factory image for my device by following this guide: http://forum.xda-developers.com/showthread.php?t=2513701
And it started to work perfectly, till now........
after about a week i watched a unspecified video on Google Chrome and the screen freezed ( not literally )
So I hold the power button and turn it off, turn it back on and i got a infinity bootloop.
So I flash again the official factory image and it can't flash my system?
its look like this;
trying to flash system.img....
FAILED
the rest of the process flash succesfull until it reach system.img
and a friend of mine therinsem tried to add a custom recovery and it didn't work, so we flashed again the factory image and it still FAILED,
to flash system.img the rest of the process work until it reach system.img.
now it doesn't even boot? it's only going straight into fastboot-mode
and if i press in fastboot-mode recoverymode than it shows nothing? ( i think because we tried to flash a custom recovery )
- iv'e tried on a bunch of diffrent windows laptop's
- i can't access the internal storage of the device
- i can still '' side-load'' I think
so this is my problem with the nexus5, does anyone have a solution?:crying:
Download the factory image again and make sure the md5 checks. Then try again
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
dicecuber said:
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
Click to expand...
Click to collapse
What? Who's taking about imei?
jd1639 said:
Download the factory image again and make sure the md5 checks. Then try again
Click to expand...
Click to collapse
Thank you for a answer! i will try it and will give a update status soon.
jd1639 said:
What? Who's taking about imei?
Click to expand...
Click to collapse
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
Click to expand...
Click to collapse
Sometimes it happens that you lose your imei. Flashing the factor image can bring it back. Nothing nefarious going on
dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Click to expand...
Click to collapse
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
^someone suggested Op rma it. I suggested he refrain from doing that
Sent from my Nexus 5
theesotericone said:
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
Click to expand...
Click to collapse
theesotericone said:
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
Click to expand...
Click to collapse
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
tomaszcs said:
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
Click to expand...
Click to collapse
Formatting system did not work.
I helped Tomasz doing this
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:
Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...
Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.
No worries
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood
rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?
Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.
Yup. RMA
Sent from my Nexus 5 using Tapatalk
Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?
You_got_owned123 said:
Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?
Click to expand...
Click to collapse
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.
bitdomo said:
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.
Click to expand...
Click to collapse
Sad to say, I've already tried that.. Even tried to flash stock cache image.
You_got_owned123 said:
Sad to say, I've already tried that.. Even tried to flash stock cache image.
Click to expand...
Click to collapse
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?
bitdomo said:
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?
Click to expand...
Click to collapse
I've flashed radio, but modem I have not. I'll have to try that!
You_got_owned123 said:
I've flashed radio, but modem I have not. I'll have to try that!
Click to expand...
Click to collapse
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...
rootSU said:
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...
Click to expand...
Click to collapse
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
See my signature
Sent from my Nexus 5 using Tapatalk
You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
Or check my signature.
Someone calls it modem and someone calls it radio.
rootSU said:
See my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
I help a lot of people. I cannot pick out individual instances.
Use LG flashtool
Sent from my Nexus 5 using Tapatalk
You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.
bitdomo said:
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.
Click to expand...
Click to collapse
Perist will not mount. I hasn't seen factory image for persist partition.
You_got_owned123 said:
Perist will not mount. I hasn't seen factory image for persist partition.
Click to expand...
Click to collapse
Because there arent any. It is unique for every device like efs.
bitdomo said:
Because there arent any. It is unique for every device like efs.
Click to expand...
Click to collapse
So is that a problem?
You_got_owned123 said:
So is that a problem?
Click to expand...
Click to collapse
If you see that /persist cannot be mounted then it could be.
bitdomo said:
If you see that /persist cannot be mounted then it could be.
Click to expand...
Click to collapse
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.
You_got_owned123 said:
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.
Click to expand...
Click to collapse
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.
bitdomo said:
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.
Click to expand...
Click to collapse
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.
You_got_owned123 said:
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.
Click to expand...
Click to collapse
It would be nice if you would post how did you solve your issue. Some will learn and it could help others having the same issue.
My phone randomly shut off and then I when I turn it back on. the infinite boot logo appear. I installed clockworld. tried to reformat everything and reinstall stock image and still nothing.
Need more info. What does still nothing mean? Flashing the stock images failed?
Sent from my Nexus 5 using Tapatalk
See here for a possible (probable) solution
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
ldubs said:
Need more info. What does still nothing mean? Flashing the stock images failed?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry I should of added more information.
I followed the guide that google gives to flash the ROM using the original stock image cant post link since I am a new member
it failed still having the endless boot animation.,
also my problem is I didnt had usd debugging enabled. So its make hard to use some of the ADB Commands
Google's guide (flashing the zip file) often fails, not sure why. Look in my guide for a better way to do this. Though if you have a persist partition corrupted, flashing Lollipop will not help. You will still not be able to boot. See my guide. Good luck!
eross said:
Google's guide (flashing the zip file) often fails, not sure why. Look in my guide for a better way to do this. Though if you have a persist partition corrupted, flashing Lollipop will not help. You will still not be able to boot. See my guide. Good luck!
Click to expand...
Click to collapse
(when I do ADB devices. Dosent display my device. I was able to do everything from the guide I am at the part where I have to fix the partition persit) NVM ABOUT THAT
eross said:
See here for a possible (probable) solution
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Click to expand...
Click to collapse
it worked thanks!!! I was about to send it to LG
darthzash said:
it worked thanks!!! I was about to send it to LG
Click to expand...
Click to collapse
Great!