Related
okay. i decided to buy the A500 tonight. after reading all the threads, it sounds like a good purchase. but when i looked at the demo they had on the showroom floor, it had a password on it.
i don't plan on putting a password on it. i just want it next to my bed and not have to worry about it. what i'm worried about is someone (like a friend) putting a password on it. the reason i ask this is because when i was looking at the demo model tonight, no one knew what the password was...so i "soft" reset it via metal wire into the reset hole AND also by holding up on the volume rocker. but in either case, it didn't do anything except for pop up the Android guy with an exclamation symbol. when it rebooted, it was at the password lock screen again. nothing changed.
after looking here for related threads, it says that if you don't know the password, then you're in deep kaka doodie (it has to be sent back to Acer).
i don't know how many of you still remember what CMOS is, but in order to set a boot password, you have to know the master password (which you need to know in order to make any CMOS changes to begin with. such as enabling the boot password option). that way the person who built the computer will be the first and only person to set the master password, preventing his/her jerk friends from pulling a prank by preventing him/her from booting their computer.
so my question is: is there a "master" password required to set the lock screen password?
my phone has a password/pattern. the reason i have it is because i leave my phone at my desk at work or on the coffee table at my friends. and i don't want them looking at my stuff. but the tablet is gonna be in my room and i don't have to worry about anyone looking at it or stealing it except for myself.
another question: will the custom roms bypass this password feature?
thanks for reading this far. sorry if i'm asking stupid questions, but i guess after the frustration at the store tonight with the demo model, i'm a bit annoyed. i never got to actually use the device and i still bought it anyways on the grounds that i would be happy with it (that sounds dumb now that i think about it). heck...its still sealed in its box & sitting on my bed as i'm typing this. but the password feature really sounds like a danger.
EDIT: the reason i'm asking this right now is because i JUST opened the box and am now charging it (for at least the recommended four hours), but i'll be asleep in a couple. so i won't find out til morning. but i'm hoping an XDA boarder can fill me in before i catch some Zzzs.
As far for a master password I've no idea if there's one...
Regarding installing new Roms, yes it will reset the password. I don't know if it's because the CWM wipe and factory reset but it will clean any password you have set.
You can use the tablet without any password. It's very easy to set it up under adjustements/security.
And I do agree with you that having a demo pc/tablet/phone is the most idiotic idea of marketing or sales strategy I can think off.
I've got my Iconia for 5 weeks now, gone trought a few roms, got back to stock but in the middle I've learned the "how to..." At the end I'm so happy with this tablet and how flexible is that I'm recommending it to all my friends.
Hope that helped.
Cheers,
very helpful. thank, mate. cheers!
just for your info, the ICONIA A500 is delivered without any obligation of using any passwords of any kind. In the showroom they have encrypted the tablet to protect it it from any unauthorized use.
In fact only if you want to whether protect your tablets content to be visible if ever it is stolen, or if you want to use enterprise (exchange activesync push) email capabilities, you have to encrypt your device, which then will oblige you to enter a master password during startup and a PIN password to exit sleep state.
So of corse no password protection except if you want it.
Hello to all good guys in xda-developers forum.
This is my very first post and I really feel desperate and need your kind help.
New Acer iconia with stock firmware 3.2.1 was nicely running this morning until I tried to root the device.It was supposed to be very simple process and not to get into dirty complicated procedures but the gingerbreak.apk did not work as expected so I tried alternative methods.What I read in various forums was that the gingerbreak application is not able to root the new firmwares version so I tried to downgrade the firmware to 3.0.1.
Downloaded the Acer stock recovery firmware EUUs_SBK_Acer_A501_0.017.01_PA_ATT.exe and attempted to flash onto my tablet .I think I did all necessary pre-installation checks.The process started but it stopped on 10 percent for about 30 minutes without any progress.Only Acer logo was displayed and 'entering file downloading mode' at the top of the screen.
After long time no change I finally gave up and unplugged the device from the USB port and restarted but nothing works since then.
1. No vibration on Start
2. Black screen
3. No new USB device appear on my PC
4. No sign of any activity other then power button light
I guess the original firmware was wiped but the new firmware was not flashed...for whatever reason...perhaps the worst scenario.
I will really appreciate If anybody may give me advice how to fix it.
So it turns on but does not display anything? Have you tried to hold the power button and volume down button at the same to when you turn it on to try to get it into recovery. Also there is a little reset button on the side you can try to push.
Sent from my A500 using xda premium
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
acera500 said:
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
Click to expand...
Click to collapse
Try this thread. Look about halfway down, and you'll see almost the exact thing you did, and how this guy got it going.
http://forum.xda-developers.com/showthread.php?t=1291747
Basically you can run a search for APX in the main forum threads and find some other posts, but hopefully this will get you going.
I pulled this from the general forum (eventually), but you can also search the Q&A main forum page as well, and the dev forum.
Another link;
http://forum.xda-developers.com/showthread.php?t=1255519&highlight=apx&page=2
If its new just return it to the store for another one.
Sent from my A500 using xda premium
Acer or the store did not brick it
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Piece of cake to fix if you kept you USB serial number (from the downgrade tool)???
===== If you have your USB serial number ====================
1. Lets assume you know your USB serial number. If not, then you might be able to get it from your registry.
2. Download my flashing tool at http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
a. Open up the readme.pdf for the instructions on how to flash
3. KEEP your acer unplugged and run the program
4. The program will install the APX flash drivers and will tell you to plug in the USB. Ignore this step. It will not work. In the instructions skip steps 3, 8, 9, 10.
5. Eventually the flashing tool will timeout because you do NOT have the tablet connected. It will then display a message box telling you how to use a paperclip and the power button to get you into APX mode. THIS IS THE secret to getting the tool to flash your ACER. However, once you get it into APX mode you will need your USB serial number (without it, you are fubar).
a. Plug in the tablet to your computer with the USB and paperclip yourself to fastboot.
6. Now in step 11, enter your USB serial number
7. Now just follow the rest of the instructions.
====== NO USB Serial number ==========
If you do not have your USB serial number than you are going to be out of luck, unless you have ever connected the device to your computer. If you did, then your registry will have a history containing your serial number.
Google usbdeview tool and download it. This will show the serial number of any USB device you've connected to your computer.
===== No Serial number, never connected it, what to do ==========
If you have no serial number and cannot get it, then hopefully you can get to recovery mode (power & volume) and flash using a signed update.zip from ACER. Download one of the update.zip's and put it on your external SDCard and then boot to recovery.
=== Bricked and No serial number, never connected, and you fubar'ed the recovery image ===
If you never connected your table to the USB and your computer to get the USB serial number then you are NOT going to be able to flash it to fix it.
If you fubar'ed the recovery image then you won't be able to get into recovery to run the ACER update zip.
At this point, you can still get your tablet into APX fastboot mode using a paperclip and the power button. But I know of NO way to flash it without the USB serial number and I know noway to get the USB serial number from the APX driver. I've tried and looked at getting the serial number from just APX mode, but I cannot determine how to get it. Someone out there might know.
Hope this helps,
TD
Your CPUID can also be found in the uid.txt file in your cwm backup folder - /mnt/external_sd/clockworkmod/backup/ - just remember to drop the 0x when you need to enter it
erica_renee said:
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Click to expand...
Click to collapse
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
wade7919 said:
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
Click to expand...
Click to collapse
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Why locking a bootloader will cost ACER billions
Moscow and wade7919, you both make good arguments.
But it is what point of view you're coming form. If I bought a car and changed the RIM's on all 4 wheels and the engine blew up, would GM refuse to honor the warranty?
However, if I put jet fuel and alcohol in for gasoline and blew the engine why would they honor the warranty?
So, the question here is does rooting a device cause actual damage to the device thereby preventing rooting saves them warranty issues? Or is the device also considered to include the software and is covered under warranty?
I'm not taking sides here, but you both are making very good points but with different examples at different points of view.
So, lets look at other items and see if we can draw a parallel. If I buy a brand new Dell computer and send it in for Warranty and there is nothing wrong with the hardware they charge me (correct?). So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty.
So, why does an Android MFG take the warranty one step further and include the OS and take steps to lock it so you cannot change it? Well, this is because nobody owns the OS (it's open source) therefore they take ownership of the build. Because there's no Microsoft to blame, they lock the software and consider it to be part of the overall device (Apple claimed this in their lawsuit). So, in the MFG's mind, there is no difference from the screen, keyboard, or the firmware & software.
So the question is what do you think should be covered under warranty? Most people think it should be just the hardware like a PC. Others see the whole device which includes the OS.
My point of view:
What follows is my rant and my opinion (you are warned )
In my opinion, I had NO problem until they decided to lock the bootloader. I have no problem with them claiming warranty from A-Z and if I change anything they won't warranty it. No problem, I understand that and accept full responsibility. But by ACER locking the bootloader they went too far.
To me this would be like GM welding the hood shut on my car. Better yet, it would be like me waking up one morning and opening my garage to get in my car and discover that during the night GM welded the hood shut. This, in my opinion, is illegal. Matter of fact, in my opinion, it violates US Federal hacking laws because they enter a system and destroyed data. I eventually think OEM's will get a class action suit filed on them for this.
Secondly, Windows 8 is going to be the game changer. OEM's can now make a hardware device and sit behind only warranting the hardware. You have a problem with the OS, call MS. Also, there is a HUGE (I mean HUGE). Did I mention HUGE, demand for tablets in business. Businesses will NOT put a device that has all these consumer games and social networking loaded into the workforce. There are billions in business applications that can be made, but you cannot sell them if they only run on a tablet that cannot have games removed etc.
Example might help: Medical field <- Think of all the applications a tablet can be used to save costs in hospitals. Do your really want your doctor or nurse etc using this tablet on facebook? Insurance company's, law firms, retailers, traveling sales, etc etc (Government). The list goes on.
Developers will see this huge opportunity and will write applications because they can sell them to A-Z and the business buying them will buy them because they can remove facebook and gmail from their company owned tablets. Now, as more and more developers move to Windows they'll drop Android. Want another example, read about Netflix and the issues they have had supporting a fragmented Android OS. So, business applications will move to Windows, but you might say so what, the consumer market is still there. True, but all you need is one killer application that everyone will want and for that to only be on Windows 8. Want some examples, here's my list, NFL (or sports), Netflix, Skype (gee owned by MS now isn't it?), or something new.
Bottom-line is this, if ACER and the others want to lock their bootloaders then they have just taken themselves out of the game for any business sales. Can you imagine walking into a boardroom showing the Government how your new VA application will save the VA Hospitals millions next year alone and improve veterans healthcare. Your application runs on any HC Android tablet. Everything is smoking, going great, as you hand your tablets, ACER a500', around the room. They are loving it. You just hit 'pay-dirt', then someone says hey I see these ACER's have gmail, facebook, blah blah. We cannot have government employees using tablets with those applications loaded, your installer removes them doesn't it? Silence enters the room, all eyes are focused on you. Your mind see millions escaping which were just within your grasp, you pause, you think, and you say YES General as you grab your Motorola Xoom and say 'that's why we recommend you buy nothing but Motorola.'. ACER just kissed millions in sales goodbye (oh and this is a true story).
i do believe acer should lock the bootloader on there devices.
However thee are things I would be doing with my tab if it were not locked.
Acer should give us the ability to flash the bootloader and not use the proprietary software. Lock that software to there bootloader.for there protections.
Give us a wway to unlock it..AT OUR OWN RISK..
So it should be locked but have a way to unlock it with the end user understanding they are totally on there own ..
I would be OK with voiding my warranty.
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Moscow Desire said:
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Click to expand...
Click to collapse
Very well put.I do know of a few people who have sent there device to acer after messing it up installing rom and telling acer.acer still fixed it free.
Honesty is always best
The evils of rooting
I'm still missing something here, why locking a bootloader does anything. Go get a Mortorola Xoom (not the FE) and you run the unlock OEM. It tells you that you are unlocking it. It tells you that you unlock it at your own risk. You cannot relock it until it is 100% back to stock. It asks you three times are you sure.
Locking the bootloader and treating everyone as an idiot is the problem. Just do what Motorola does, and stop being everybody's keeper. If they want to 'Police' this then you should have to call ACER and they fax you a form. You give DNA to prove who you are and fax it back. Then you go to a mandatory rooting class, that lasts for 5 days, where ACER preaches to you the sins of rooting. Then you have to take and pass a test. Then and only then, after passing the test you get a certificate. Then you call back, give them your certificate ID. Now they give you the secret key to unlock only your tablet.
That's the ticket,
TD
Bottom-line, it's not that they locked the boatloader, it's that you cannot unlock it. Like I said, go out to your driveway some morning and find that GM welded the hood to your car shut because they think you are stupid and shouldn't be opening the hood. Mind you that YESTERDAY, and at the time your bought it, it was not welded shut. That ladies and gentlemen is what ACER did with their OTA.
Moscow Desire said:
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Click to expand...
Click to collapse
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
wade7919 said:
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
Click to expand...
Click to collapse
I still like my car comparison
I make the car comparison to illustrate a point, because when I compare tablets to a PC everyone piles on *****ing about MS.
Bottom-line it doesn't matter if it's a blender or a PC. I own it, you own yours and I can do what I want with mine as you can with yours. Now, again I have a BIG(did i mention BIG issue with them changing it on me after I bought it.
To get back on topic, is the original poster still out there?? Has any of this helped? Are you still bricked?? Give us an update so we know if anything worked or you still need help.
The device was returned and accepted for replacement by the shop.Got new one and feel very nervous to start rooting procedure over.I was really lucky that they did not charge me anything but I really want to know what I did wrong so I don't brick my new device again.
I will provide further details soon about my computer OS and firewall settings and perhaps we may figure out what I did wrong.
To all good guys who send me them suggestions and solutions I wanna say big THANK YOU !!!
Your help is really priceless and thrilled me deeply. Will update topic soon
Happy New Yer to all Android fans!!!
So...Back on the subject.
My device was purchased in Japan and its current firmware version is
Acer_A500_7.009.03_AAP_CUS6JP
Q1. Can I flash US or World Wide firmware version on that device.
Q2. Does anybody know the Acer's ftp download server address for Japan
Q3. I think its a good idea to dump my original stock firmware but it seems there is no way doing that prior rooting.So..kinda stuck .any suggestions appreciated.
P.S. I'm thinking about flashing the latest Rooted rom 3.2.1 V3 by timmiDean (thanks for your hard work) I read the instructions very carefully and I think that everything will go smoothly but just in case (considering the specific Japanese firmware version)
would appreciate any further directions by the author.
Thanks
URGENT HELP NEEDED
SEE FULL PHONE SPECS AT BOTTOM OF POST, which I have managed to claw together in the last 24 hours ... I am giving you guys as much info as possible, so you know what I have done, tried, what has failed & what has worked; Even if only partially! Rather more info & you guys can skim, versus too little info!
Dearest Distinguished Fellow Geeks, Friends, Developers & GOD's a La Tech!
I'm @ my wits end & bloody terrified right now (And if you read the background on me below, you will realize that it must take a calamity of EPIC proportions to get me remotely upset & additionally, I have never EVER before been so clueless in terms of something IT related & therefore, this is the first time in my whole life that I am posting to a forum) - if I'm blatantly honest wif ya all & PRAY someone can help me or guide me 2 help!
I could be a developer myself, as one of my god given talents, happens to be a qualified advanced & senior tech specialist, BUT NOT much of Unix, Linux & I have barely been learning on Android, for the equivalent of a YEAR, as a newish convert from iPhone - That said, I have NOT & WOULD not take a step, without first researching at least half a dozen reported user experiences and/or answered/RESOLVED technical user replies & their explicit advice, followed with my own weighing of the Pro's & Con's FOR ME, based on my personal & business needs (I weigh Pro's & Con's old school style; on a block of A4 Lined Paper & if I establish a RISK @ or OVER 60%, in terms of Android/Linux/Unix, I would NOT change a thing, before making a novice mistake, such as this appears to be!
NO Android expert, but I am equally NOT naive! I only moved to Android from iOS at S3, however, I did manage to Root my current "S4" via code & managed to do it without much difficulty ... The REAL problem began last night, when a new app I downloaded which was meant to show me WHY I was suddenly getting ERROR msg after ERROR msg that I had no more internal space (That I would not get new SMS, that hell was about to freeze over and so on) & that with EVERY APP that can be on an SD card, on mine, and having only the essentials on the Internal, so as to keep the internal components running optimized at all times. I am meticulous about maintenance & permissions repairs.
First, some background about me, to help you understand my level of expertise - My technical field of expertise is a combination of self taught, work/career related trained or post secondary schooling certifications, for example WIN/DOS (Graduate of half a dozen MCSE etc Certifications, with no less than 98% Average) - Thereafter, I naturally gravitated career-wise to the PC-Hardware side - I learned on the fledgling ancestors of todays Internet, before the internet took off (& whilst I am no longer working due to substantial disability, I have managed to keep my IT skills sharp as Needles) first, in my early mid-teens @ Canada's then most technologically advanced Internet Provider, Bell Sympatico, thereafter promoted up technically to Bell Nexxia for Corporate Internet & High Level Resolutions, never before seen at the time, which then lead to me being headhunted & promotion to Global Crossing & being privileged to be a part of IT history, by being a part of their backbone; For those unfamiliar, GC was the BIGGEST & at that time MAIN company responsible for laying the Fibre under the Oceans we use to do EVERYTHING we do today! Later, I worked for Dell & was specially trained & Dell Certifications @ Stage 4 Tech Level (Highest Dell internal "Dell-On-Call" Expert level tech, at the time I was employed there) ... I am a child of the Internet & Computer Age at 34 years of age & my first memories, are not of when I first walked or spoke one of the trilingual languages I was simultaneously raised with, but rather of sitting on my dad's lap, as he feverishly worked on his then, over $50,000 expensive, room sized computing outfit, which kickstarted a lifelong & ongoing fascination with ALL things IT. At home I always had a Mac alongside my PC & became famous for being the first person in the world to program & allow a Mac to dual boot into Windows - A story that was extensively covered by the media at the time, as MS & Apple were NOWHERE near what I had achieved & anticipated the same result "hopefully" within a year. I became one of the main consultants to BOTH to create what became known to the world as "Bootcamp" & was privileged beyond belief to meet my idols, Steve Jobs, Bill Gates, Captain Crunch & Wos! Today, I still have my dual boot MacBookPro sitting next to my PC, despite Windows having ALWAYS run better on Apple's hardware, than ANY competitor PC hardware maker I have EVER tested or used! Hacking software & making it work with hardware outside the concept of their makers, was ALWAYS my biggest ambition; Essentially, discovering how things work and/or don't - Learning by trial & error, if you will & that has always been my motto & thus far, it has only enriched my technical capabilities! ...
... That is; Until last night & today! ...
So I was suddenly forced to select & place my faith with a highly rated App from the Play Store (Unknown APP Developers was NOT yet checked, as mentioned in more detail below) - Sadly, I cannot tell you which APP it was, cause suddenly the action it recommended & took me to a system crash, followed with seemingly endless Bootloop. I essentially can't get past the boot screen UNLESS I do a Reboot Recovery via ADB, with the phone connected to the PC via USB, then a wipe of the Cache & data wipe/factory reset. INTERESTINGLY, I have managed to duplicate this OFTEN, after the restart following successful Cache Wipe & Factory Reset, the phone boots to the SysUI as it did when I unboxed! That is NO PROBLEM! I have duplicated this result so often, because I have naturally tried every other technical option, known to mankind, before my last resort, this POST! INTERESTING as well, PERHAPS, is that I cannot seem to use ANY route, of the MANY, via Volume Up & Down, Home & Power to get to EITHER Recovery OR to Safe Mode! I have ONLY been able to use the buttons within Recovery AFTER a recommended Win App instructed the phone to "Reboot Recovery" - I then get the droid guy with the red exclamation mark & to get to the options, after trying all sorts, I discovered that I had to hit the Power ON/OFF briefly to have the options list show up! - Then with the use of the Volume Down button to Scroll, down, through the options AND Volume UP held longer selects the option highlighted in Recover Mode, leading for example to the Data Wipe/Factory Reset option & the foreign looking (Seeing it for the first time, I thought my phone was fawked for sure if "NO" was appearing in the list of options THAT MANY TIMES) list of "NO" options with a "YES" option & further warning beside it! - I cannot explain to myself WHY the phone will not seemingly go into Recovery manually, with any number of button press options alone & I reckon I have tried every combination of options, I managed to find on the net, YET as soon as the phone is commanded into Reboot Recovery via ADB Win App, the buttons work after the phone gets to the, CLEARLY distraught Droid laying on his side! When I try to boot WITHOUT USB into Recovery it either flashes the display and/or Boot Logo, over & over until I release and/or even makes a clicking or clock tick-like sound, combined with an endless boot logo, until I force a shutdown via EITHER holding the POWER ON/OFF button for about 10 seconds, which leads to the endless Boot Logo OR the combo of Home button & Power ON/OFF, which to the best of my recollection flashes the display ON & OFF, until released, then endless Boot Logo. I had a similar problem with my S3 after it had a fatal drop from my hand, caused by a temporary paralysis of an extremity, which is one of many side effects/symptoms of my Illness/Disability & happens without warning, HOWEVER, in the case of the S3, it would Boot Logo for a bit, then reboot itself & repeat & there was NO WAY to stop it doing that until the battery died, or was physically removed by me. So this time around, I am quite literally delighted that it will AT LEAST go into Recovery via ADB & USB & then the use of the buttons when inside & that it WILL stay powered OFF, unlike my S3 fatality. Just to be clear, my current phone has not even been left to bounce around a protective enclosure within a small pouch, NEVER-MIND a drop!
This APP I downloaded 24 hours ago was "designed" to reveal ALL internal files that IT (The APP) considered to be bloatware and/or obsolete files, clogging the internal side ... It led me straight to one file, which stood out to me, like no other, because I live in Germany & speak German. Here we have a load of so-called APPS named either "Mediatheken" or "Mediathek" or "Mediatheke" & they are VERY popular Digital Options or Features - The variants arise in German, depending on how one is describing it & how many one is speaking of! A "Mediathek" singular, is ONE way of saying, what we refer to as "Media Center" & "Medien" the other way of saying "Media" CANNOT be used in this context, because "Medien" in German is reserved ONLY for describing the traditional "media" or press NOT Media Files etc. Whereas saying "Mediatheken" or "Mediatheke" is the English equivalent of "MEDIA CENTER" with greater than one, in content & IMPLIES a tangible digital file or FILES! To define it is easier! It is nothing more than an APP or APPS, made by individual German TV networks, giving the user the ability to stream any program after it's airing (Similar to Netflix or another provider I use here, called Watchever, which allows the user to download ANYTHING for offline viewing, which is in addition to Music Streaming services which I am a client of & use on my mobile as much as I use them on my traditional computer. Those services, Ampya & Spotify, ALSO allow "offline" downloading of music, which is then logically (Or so I thought anyway) downloaded to the Internal Storage - To make the whole thing even more complex, I unboxed & setup the phone in German first & used my offline Music & offline video Mediatheken WITHOUT an SD Card until I realized, space was becoming a "life or death" situation. That would mean, theoretically, that ANY say series, movie or music I downloaded to the German Language setup phone, stored internally before I got the SD Card & it would be logical, that the created folder for the said media, would be called MEDIA which is Mediatheke in German. I changed the sys language from German to English when I successfully rooted it, well over 2 months ago now & DID NOT/forgot to switch back to German ... So whilst my phone was literally terrorizing me to uninstall ANYTHING on the internal side, via a peppering of errors I couldn't OK fast enough to be able to simultaneously get rid of ANYTHING APP wise, that is unable to be stored on the SD Card. The concept was, get rid of the NON-ESSENTIAL apps stored internally to calm the phone down & then proceed to find a solution to track down, easily, what was causing this sudden space crunch! The irony is; 95% of ALL the apps on my phone, were capable of being run & stored on the SD CARD; Meaning there was clearly more than just 2 or 3 APPS I had to quickly dump, but obviously, in my mind, there had to be STUFF on the internal side, media, that was left undiscovered by me or which were NOT auto synced to DropBox or my Google Drive. As it turned out, initially, I was correct in assuming that there was obviously **** on the internal side, which I had long forgotten about & adding an APP here or there, which HAD TO BE installed & run internally such as, one example, Facebook, plus the forgotten media, had now led to the Space Crunch! I went folder to folder to locate the media I had looked at, was sent or received BEFORE my Micro-SD Card upgrade & uploaded them all to my DropBox & Google Sync, so as to have 2 backups. BUT, even after having deleted a good 100 pictures & audio files, there was still SOMETHING I was clearly missing in terms of space usage, versus the size of the APPS now on the Internal side & their total space. Which is when I began looking for an APP to hunt down bigger files in bulk & in my panic, the app recommended I ditch a file I was named "Mediatheke or Mediatheken" - A file I thought was loaded with crap from all these various "mediathekes" due to its size; That, I thought, not only made perfect sense (after discovering all the other media pre SD Card, forgotten about & causing the Space issues) but HAD TO BE THE "ROOT" - no pun intended - of ALL EVIL! It deleted the file without so much as a warning that said file was being shared by other APPS or systems, NEVER-MIND WARNING ME of what would come next! The phone suddenly crashed & rebooted only to reach the Boot Logo & remain there, illuminating the logo just as it normally would, but without proceeding! Since the first Reboot Recovery, Cache Wipe & Factory Restore & the phone would do EVERYTHING as expected, again & AGAIN, until it finished booting & had loaded the stock SysUI & the pretty diagrams of what each thing does, which was & remains the goal, ONLY, within 10 seconds MAX I get the same Error in Grey "Unfortunately the System UI has" stopped/quit/failed/crashed" - I cannot recall, because of my illness, which if the 4 it said & BEFORE I could even hit OK or do ANYTHING at all, it auto shuts down & returns to the non-stop Boot Logo.
At first I thought I was dealing with a simply/slight corruption or error (Perhaps because of the Cache Wipe) that would surely allow me to proceed someway or another, to resolve the problem & in the course of my following non-stop research to resolve, I deduce that the corruption or error is 100% the ONLY thing causing the SystemUI to fail, thus MUST BE related to the deleted file. I was correct, it would appear! This APP had me delete something big in size, related to the SystemUI, namely Mediatek" - The difference is ONE SINGLE CHARACTER, namely the missing "H" which would have made it "Mediathek" & instead has caused me an unprecedented, epic nightmare, unlike any nightmare I have ever had, seen or heard of in my 3 decades of IT induced life! What followed has had me part terrified to death, part dumbfoundead, part mystified, part livid that such a colossal error or mistake can be allowed to proceed, without even the slightest regard for the integrity of the carefully cared for by myself, Operating System & has now ultimately left me resigned to the gut wrenching feeling of utter helplessness/hopelessness ever since ... The ERROR came in a heartbeat/blink of the eye after the file was deleted, WITHOUT any warning the file MIGHT be essential to or even shared by the system/OS or other applications FORGET a warning that I would be deleting a file that MUST be kept, was recommended to be kept or had to be kept; FULL-STOP! As soon as the error notification pops up, the phone literally reboots itself right back to square one & stays there, until I force a power cut via a long hold of the Power ON/OFF button OR by physically removing the battery, as a NUMBER of threads from you guys have instructed other's to do, in the case of Bootloops. Even more remarkable, is the fact that during the endless Boot Logo, I can attach my phone to my Windows or OSX Mavericks, at ANYTIME, without any difficulty or say lag & command it to Wipe Data or Reboot or Reboot in Recovery & after a clearing of the Cache & a Factory Reset or vice versa, tried in countless different variations & times, the phone DOES reboot & goes back to the factory ROM, YET, as soon as it shows the newly restored UI, the System UI error comes, knocking the phone back to endless Boot Logo. Also interesting; My phone doesn't seem to want to go into Safe Mode either!
To add insult to injury, I realized only in the last 24 hours that my phone is NOT a Samsung S4, rather a S4 clone (Make = Shengda - All retrievable specs I have managed to get, below, since "Shengda" doesn't seem to have it's ROM's available for an emergency, or a decent website either! I am FURIOUS that this phone seemed so good at having convinced me that it was a Samsung S4; Even the various Device ID apps I have had; Perfect example, in order to do the ROOT, the phone was identified as nothing other than a Samsung! ONLY the ADB console on my Win revealed its maker was NOT Samsung at all, but a "China phone") that looks identical to the S5, except with extra's like a Dual SIM, which was the major selling point at the time I bought it! I thought nothing other than it being a modified or supped up Samsung S4, with a S5 size screen, back last November when I bought it & no one knew that it would turn out to look virtually identical to the current S5. It was billed as a Samsung S4 "modified to higher specs & added features" like the battery, apparently the same power of the S5 batteries & 2 of them to boot: Each a much higher mAh than the S4 offered & on par with the soon to be released S5. To be frank, the phone has been a DREAM; Until NOW! I have never had an issue with it! On the contrary, I have continually had better results with IT, than Samsungs new S5 is promising ahead of it's German release next month, to give & NOT to be compared with the S4, the alternative at the time! WHO WOULDN'T HAVE BOUGHT THIS PHONE, is the only question I can pose, even now, still!
I am now at such a stage of despair, that I have long gone into "DO ANYTHING MODE" to bring my beautiful phone back to life! In my desperate search I found a website, NeedRom.com (which has MANY shout out's to XDA btw) & interestingly they have NO MENTION of Shengda BUT when I did a cross search of the EXACT ROM I have, via the Build ID, it returned a ROM from another maker I have NEVER heard of before called "Star"! I don't know a thing about how to get a working/stock ROM or "custom rom" onto the phone, with which I would hope to be able to re-install to a similar functionality that I had before. That is where I place my hope in your wonderful & endless talents! However, in the meantime, judging by the Build ID, being numerically, exactly identical to the one that was originally what I believe is called the "stock ROM" which doesn't want to reset itself to how I got it ... if my guesstimation that the clone maker "Star's" Android Build = identical to the "Shengda" one I started with, that would tell me that it MUST be highly compatible with my phone & hardware, therefore could be the EASY resolve!!!???
What makes me worry is that it REMAINS from a different maker & my lack of knowledge vis-a-vis ROM's and/or how to install/flash a Custom ROM's, plus add to that, without having some APP being placed on a phone, which is not working in that capacity YET, makes me pause, because I simply do NOT want to take a stab in the dark! I am willing to take any ROM that will work, BUT, I am sure you will respect the fact that I want to know exactly what I am to do, step by step, including where to get the necessary tools, the ROM itself & how to apply them all successfully! I know that I can Apply from ADB, or SD Card in the Recovery I can get to via USB, but I'm still confused as to how the rest works & at the least, would need help or a point in the right direction to learn how to do this successfully, no matter the time or resources required! On top of that, I DO have Odin but ZERO knowledge on how it works, which settings I would check/NOT check & what wants to be done to make the "flash" fully successful. I know that I am patient & learn VERY easily, IF I am given the right material guides or help!
Another point of confusion for an Android user of my capability, or lack thereof, is that users, along with developers seem split on whether to use Odin or perhaps Heimdall on OSX, which some say is apparently much superior & less risky (Not that my phone's risk could be any greater right now - In my opinion, my phone might be what is referred to as a "soft brick" based upon my newly attained knowledge of the last 24 hours, or it wouldn't load the OS, Restore to Factory ROM, only to fail because of the System UI!) - On top of that Needrom.com has a totally different method to get the ROM onto the phone, which of course only adds to my confusion; Which is the better or BEST way, for the phone & for me! I downloaded the exact build I spent hours hunting down, unzipped the Flasher Tools, but since the "Instructions to install the ROM" seems to have been written by a non-English speaker, or worse (Translated from some language via Google Translate & copied & pasted) as the "definitive guide" to follow to successfully flash this ROM on my phone; Essentially the instructions are so garbled & unclear to this native English speaker, that I am reluctant/worried to do it to begin with, before I give ya all the chance to help me, perhaps with steps I have missed out or which did not present themselves; My disability unfortunately affects my concentration, so if something is not as CLEAR & straight forward as you guys ARE, then I could cause yet MORE damage than has already been caused! Despite my newfound knowledge that one can apparently "unbrick" - Something that I learned a few short minutes ago & which gives me hope that my case is not as hopeless as it would be, IF I were still an iPhone user!
Guessing, with reference to IT, is FUN as a geek, I'll admit it, shamelessly, but NOT when it's the only phone I have & WILL BE ABLE TO AFFORD FOR A LONG TIME, with no chance of a contract phone or anything of the sort, because I am disabled & therefore also poor! This phone enabled me to monitor my over dozen different medications, medication doses, refill times, reminders ... It enables me to program my WELL above average NEED to see DR after DR, Specialist after Specialist & do so, without great effort, nor worry that my own Neurological Disorder, will cause me to become sicker than I already am! This phone is my medical Bible! Without it; I would be FULLY unable to manage half of what this disability forces me to live with & I PRAY to God that someone may have enough patience, understanding & love, to help me restore what is an indispensable medical asset & my ONLY means of contact with the outside world. That's LIFE, when you get struck down with the worst Pain Condition known to man or DR & my phone has been the lifeline, I cannot live without. The damage caused so far has caused uncontrollable pain attacks & pain no other person can contemplate; Yet I KNOW that the thought alone, that this is unresolvable, would do far worse damage, than anyone can possibly fathom!
So I am praying that you wonderful users & developers will be able to help ... I turned to you FIRST because I marvelled & bow before you, at the success rate of the half a million posts & threads I have read since the meltdown started, before even coming to the detailed conclusion that I am at now, contained herein, all on my own!
Please feel free to email me directly at [email protected]
May God Bless & Protect You All,
Sent with LOVE, Kindness & Admiration for you ALL! Heroes & GODS of Technology!
Thank you so very kindly!!!
Eli in Berlin
Manufacturer = Shengda
Model = GT-I9500 and inside behind the battery it says Model I9500 L
Android Version = 4.2.1 (Would LOVE to upgrade to the newest version if I have to start from scratch anyway, again, here I am not fully clear on what is involved)
Rooted - YES
Last Setting for DEV = USB DEBUGGING ACTIVE & allow unknown apps (Normally inactive for security reasons but turned on because I sent Framaroot to the phone before I deleted this "Mediatek" file to verify my Root settings)
Build ID = GT-I9500-20130904-093234
Board ID = K29W
Chipset Platform = MT89_K29W according to SRS ADB Toolbox --- YET --- the phone specs AND multiple other owners report their/this phone being mt6589 - MORE CONFUSION
Android version 4.2.1; eng.scm.1372296033; SDK17
CPU 4 cores; ARMv7 Processor rev 2 (v7l) MT89_K29W; Max: 1209,0 MHz; Min: 497,2 MHz
GPU PowerVR SGX 544MP; Imagination Technologies; OpenGL ES-CM 1.1; OpenGL ES 2.0 build [email protected]
Flash 4 GB (3.589 GB actual); 4 GB (3.693 GB actual)
Phone GSM, Dual SIM; Net: HSPA
WiFi wlan_mt6628; IEEE 802.11 b/g/n; MediaTek MT6628; AP Mode
USB Host No
SD Version: 1.1 5
KERNEL: Linux version 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jun 27 09:20:03 CST 2013
CODENAME: REL
Mainboard: K29W
BRAND: Samsung
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: K29W
DISPLAY: GT-I9500 20130627-092201
FINGERPRINT: Samsung/K29W/K29W:4.2.1/JOP40D/1372296033:user/test-keys
HARDWARE: mt6589
ID: JOP40D
TAGS: test-keys
Processor : ARMv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 2439.94
processor : 1
BogoMIPS : 2447.96
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 2
Hardware : MT6589
Revision : 0000
FINALLY, the Build Properties I got from SpecDevice.com
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JOP40D
ro.build.display.id=GT-I9500 20130627-092201
ro.build.version.incremental=eng.scm.1372296033
ro.custom.build.version=1372296033
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.1
ro.build.date=Thu Jun 27 09:22:01 CST 2013
ro.build.date.utc=1372296121
ro.build.type=user
ro.build.user=scm
ro.build.host=vanzo63
ro.build.tags=test-keys
ro.product.model=GT-I9500
ro.product.brand=Samsung
ro.product.name=K29W
ro.product.device=K29W
ro.product.board=K29W
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=SHENGDA
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=MT89_K29W
# ro.build.product is obsolete; use ro.product.device
ro.build.product=K29W
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=K29W-user 4.2.1 JOP40D eng.scm.1372296033 test-keys
ro.build.fingerprint=Samsung/K29W/K29W:4.2.1/JOP40D/1372296033:user/test-keys
ro.build.flavor=mt89_k29w_s8041_shengda_jb2_sw_mul
ro.build.characteristics=default
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB2.MP.V1.3
ro.mediatek.platform=MT6589
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB2.MP
ro.mediatek.version.sdk=1
# end mediatek build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ril.specific.sm_cause=0
gps.solution.combo.chip=1
ril.external.md=0
fmradio.driver.chip=3
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
ril.radiooff.poweroffMD=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
mediatek.wlan.chip=MT6628
mediatek.wlan.module.postfix=_mt6628
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
qemu.hw.mainkeys=1
ro.init.screen_brightness=240
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# begin adupsfota properties
ro.adups.fota.oem=Vanzo
ro.adups.fota.device=GT-I9500
ro.adups.fota.version=GT-I9500 20130627-092201
# begin adupsfota properties
debug.sf.hw=1
persist.sys.ui.hw=1
windowsmgr.max_events_per_sec=120
wifi.supplicant_scan_interval=300
The bible and XDA dont give support to clones
Hi,
There is only one place on XDA that may be of help...
Look HERE
This topic is a joke right?
devilsdouble said:
This topic is a joke right?
Click to expand...
Click to collapse
I don't think the longest post on xda is a joke!
However since he needs help, we should help him
That's what the rules of xda say
Since I am not better than him, I'd request somebody to please help him!
EliYakov said:
I could be a developer myself, as one of my god given talents, happens to be a qualified advanced & senior tech specialist
Click to expand...
Click to collapse
I am sure you can figure it out yourself :good:
1. Too long, didn't read.
2. We don't provide support for clone devices for a variety of reasons but mainly because they usually have vastly different specs from their real counterparts and often solutions that work for the real phones won't work on the clones.
Thread closed.
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
OP's 2nd post deleted - no need for it. Just edit Post #1
LenAsh said:
OP's 2nd post deleted - no need for it. Just edit Post #1
Click to expand...
Click to collapse
where are or name from other post, this thread is very important for us research and i think could useful.
thanks for advance.
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
JuStAdsor said:
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
Click to expand...
Click to collapse
I don't really understand the issue here, can you confirm that the tablet is still active cf. not hit by the killswitch? Why would you get an apx connected message? On a working tablet you would be directly send to an adb/fastboot interface? Usually only the killed tablets would be recognized as apx when you then connect it to a pc.. People are looking for a solution on how to nvflash via apx mode, which is an nvidia proprietary protocol and probably won't be pushed any time soon, if ever.. Possible solutions are moving to linux at the moment, where people try to connect their bricked tablets in apx mode hoping that linux would recognize the drivers, eventually, and maybe use open source universal flashing tools to recover their bricked devices..
doomedromance said:
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
Click to expand...
Click to collapse
Yes, your tablet is still alive because you flashed another rom (and that's exactly what you should do to be sure to never get hit by the kill switch) - it is very likely that the kill switch isn't triggered immediately, and than the silent update might not hit immediately neither, you're very lucky, most of the people were hit in very few hours, they couldn't even get their research done before the trigger - that said: the best way is to root the old tablet before setting up the new one, and deleting tegraota.apk and its parent directory - as explained in bogdacutu's thread in this very forum, and/or flashing a new rom to not have any nvidia apps anymore.. You can do both if you even use multirom port for nvidia shield tablet.. I can manifest that all this is working since i did it - i tryed it all and do have 2x tablets now like many others too
This isn't cool man, why steal from Nvidia? Or from anyone. Stealing is not OK.
Sent from my SM-N910T
not stealing XBlack, my tablet was getting hot before recall...I did researched and spent time and efforts to fix the issue which i did. Nvidia sends new tablets to cover their ass for potential law suites in case of a situation happening again. Specifically states to dispose or return and why return if they will dispose for you? Why dispose of a tablet when the user fixed it by the user community. Is it taking advantage YES, we are smart people, we fix it. It was their choice to send new tablets without having to receive old ones prior. In no way is it stealing, tucking it in my pants and walking out of a Best Buy or FRYs without paying for it is stealing. We as a community with fixed tablets can be looked at as beta testers who get to keep their prototype and are given a NEW updated consultation model. Pretty much sums it up you can look at it in any way you like but we as a smart community in no way are criminals that steal from NVIDIA. Thanks NVIDIA i will forever be a loyal customer who buys your products since i think they are great. thank you for my new updated tablet.6
The problem is if you "fix" the tablet and then give it to else, and it catches fire, will nvidia be liable? They want the defective devices off the street, not disassembled and reassembled with non spec parts by potentially incompetent consumers.
Sent from my HTC M9 using Tapatalk
Hi all - I imagine this has been asked a thousand times before, but I am new here and in need of some real help.
My brother recently passed away, and his phone (Huwei P Smart 2019) mysteriously went into Airplane Mode, and has no sim card. The lock screen is on and none of the 'usual' numbers or patterns he used appear to work. This phone was his lifeline before he died, using it to speak to doctors and care workers - which is why I do not think he set it to airplane mode himself.
Shortly after he died a 'friend' went to his house to 'secure valuable belongings' and he had my blessing to do so. When I managed to get there, and secure those belongings myself, lo and behold the phone was locked.
Apparently, it does this when it powers up after the battery drains. Apparently, (according to the 'friend') on a reboot it shows a lock screen... and somehow goes into airplane mode. All I know is his two other older android phones do not have passcodes and all are open and accessible after a reboot - I've already been able to check these for data easily enough. I cannot even see what version of the OS is installed, but I'd guess it is the default that the phone came with.
I am not an Android user, and am certainly not a 'power' user of any device, so I don't know if what the 'friend' is telling me is total BS or not. What I do know is there is likely to be some essential information stored on that phone, let alone photos and memories that his family would like - I am specifically looking for any details of his medical treatments and messages he might have received just before he died.
I've trawled around countless 'phone repair' booths in countless malls, and everyone tells me the same thing - it can be opened, but you have to wipe the phone. Obviously, I don't think that'll help as a) I don't want to reuse the phone and b) I need the data from it to help with an ongoing case.
So, the question is, can it be done... and if so, how?
Thanks in advance to all who reply.
Not sure if I believe the story.
Probably with testpoint, with unlocktool, with chimera, with EFT dongle.
I've tried some methods the testpoint methods I tried all erase the data.
All other working methods are on youtube search for huawei frp without data loss and similar search strings, and click on Related videos.
Don't connect the Android to Internet to avoid security update.
Try the method with sim card with PIN however that may need a previous version security.
If there is important data wait some time and check youtube again however there are fake videos on there.
If it's too important probably someone can attack it through some method.
However if you have no good reason to attack this device better move on I do not believe the story with deceased relative and whatever is on the device maybe it's water under the bridge move forward. If not then it is a high cost in your time effort money patience better invested elsewhere.
Whatever the case not judging